On Windows, the proxy server address and port sit in one of three places. netsh winhttp show proxy prints the system proxy that services use. The ProxyServer value under Internet Settings in the registry holds the one browsers and most apps use. $env:HTTPS_PROXY shows the one for command-line tools. Empty in all three means no proxy.
We ran every command below on a Windows 11 PC in Windows PowerShell 5.1 on 20 November 2026, first with no proxy set, then with a QuanticData proxy line. The output is real; exit IPs are masked and USER and PASS stand for the credentials.
The three places, and the command for each
| Where | Who uses it | Command that prints it | Our PC printed |
|---|---|---|---|
| WinHTTP system proxy | Windows services, updates, some installers | netsh winhttp show proxy | Direct access (no proxy server). |
| Internet Settings, per user | Browsers that follow Windows, and most desktop apps | reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | ProxyEnable 0x0, no ProxyServer |
| Environment variables | curl.exe, Python Requests and other command-line tools | Get-ChildItem Env: | Where-Object Name -match 'proxy' | nothing |
A proxy set inside one program, such as a browser with its own proxy settings, a scraping script or an antidetect profile, appears in none of the three: it lives in that program's settings or in its code.
Step 1: the WinHTTP proxy with netsh
Open Command Prompt or PowerShell and run:
netsh winhttp show proxy
Current WinHTTP proxy settings:
Direct access (no proxy server).
"Direct access" means Windows services go out without a proxy. When a WinHTTP proxy is configured, this is the command that prints its address, port and bypass list (Microsoft documents it under netsh winhttp, linked below).
Step 2: the proxy browsers and apps use, in the registry
The proxy you set in Windows Settings for your user is stored under Internet Settings. Two values matter: ProxyEnable (1 when a manual proxy is on) and ProxyServer (the address and port, as host:port). A third, AutoConfigURL, holds the address of a PAC script when the proxy is chosen by a script instead.
Get-ItemProperty "HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings" |
Select-Object ProxyEnable, ProxyServer, ProxyOverride, AutoConfigURL
ProxyEnable : 0
ProxyServer :
ProxyOverride : <-loopback>;<local>;localhost;*.local;127.*;10.*;172.16.*;...;192.168.*
AutoConfigURL :
On our PC the manual proxy was off and there was no PAC script. ProxyOverride is the bypass list: the addresses that never go through the proxy.
To ask Windows which proxy it would use for one URL, after the PAC script and the bypass list are applied:
[System.Net.WebRequest]::GetSystemWebProxy().GetProxy("https://ipinfo.io").AbsoluteUri
https://ipinfo.io/
When the answer is the URL itself, as here, the request goes direct. When a proxy applies, the answer is the proxy address and port.
Step 3: the proxy of command-line tools
curl.exe and Python Requests read HTTPS_PROXY and HTTP_PROXY. We set HTTPS_PROXY to a Residential Basic line for one PowerShell process and ran curl.exe without any proxy option:
$env:HTTPS_PROXY = "http://USER:PASS@residentialboson.quanticdata.io:10000"
$env:HTTPS_PROXY
http://USER:PASS@residentialboson.quanticdata.io:10000
curl.exe -s https://ipinfo.io/json
{
"ip": "x.x.x.x",
"city": "Bridgeport",
"region": "Connecticut",
"country": "US",
"org": "AS6128 Cablevision Systems Corp."
}
curl.exe -s --noproxy ipinfo.io https://ipinfo.io/country
IT
The variable alone sent curl.exe through a home line in Connecticut; with --noproxy the same window answered from our own line in Italy. So when a tool goes through a proxy you did not set in the tool, print the environment: that is usually where it is.
Proxy address, port and exit IP are three different things
| Term | What it is | Example from our test |
|---|---|---|
| Proxy server address | The host your device connects to | residentialboson.quanticdata.io |
| Port | The door on that host | 10000 |
| Exit IP | The address websites see | x.x.x.x, Bridgeport, Connecticut |
Windows settings, apps and scripts want the first two, written as host:port. The third changes with the session and the country, and you read it from the outside by sending a request through the proxy, as in the curl.exe example. In PowerShell, a System.Net.WebProxy built from a gateway splits it for you: .Address.Host printed residentialboson.quanticdata.io and .Address.Port printed 10000.
Which of the three a program reads
Finding an address is half the job; the other half is knowing which program reads it. This is what we saw on the test PC:
| Program | Where it took the proxy from | What we ran |
|---|---|---|
| curl.exe | HTTPS_PROXY, unless -x or --noproxy is given | Exit in Bridgeport with the variable; our own line with --noproxy |
| Python Requests | HTTPS_PROXY | A plain requests.get() with the variable set answered US |
| Windows PowerShell 5.1 (.NET) | The system setting, through GetSystemWebProxy() | Direct, because Internet Settings had no proxy |
| A browser started by a script | Its own launch options | Our Playwright runs passed the proxy at launch |
So when a program uses a proxy you cannot find in Windows settings, look in its environment and its own options before anything else. Once you have the address, read where it exits: how to check a proxy IP address shows that step and what each field of the answer means.
Where to find the address of a proxy you bought
A proxy service gives you the address in your dashboard or in the line it generates. Ours comes as one line, http://USER:PASS@HOST:PORT, from the dashboard or from the generate_proxies tool of our MCP server:
| Plan | Proxy server address | Port in our tests |
|---|---|---|
| Residential Basic | residentialboson.quanticdata.io | 10000 (HTTP) |
| Residential Premium | residentialpremium.quanticdata.io | 8080 (HTTP) |
| Mobile | mobile.quanticdata.io | 8080 (HTTP) |
SOCKS5 is offered on our networks too (see SOCKS5 proxies); the ports above are the ones we used in these tests. The username carries the country and the session, so the same address and port served the US and German exits in our tests. Residential Basic and Premium give home IPs in the country you pick, and Mobile gives carrier IPs; the plans are on our pages for residential proxies and mobile proxies, and there is a Residential Basic free trial.
When the address is right but nothing loads
- A 407 answer means the address and port are right and the login is not: see 407 Proxy Authentication Required.
- The wrong place: a value in the registry does not reach curl.exe, and
HTTPS_PROXYdoes not reach the browser. Set the proxy where the program reads it. - To check a line from outside your PC, paste it into our proxy tester, which reports the exit IP, the place and the response time. The full list of causes is in our proxy not working checklist, and how to use a proxy with curl covers the command line in detail. If the goal is to hide where you are, read how to hide your IP address.


