TL;DR: A proxy extension can change only the browser’s egress while desktop apps still use your ISP. A system VPN usually rewrites the whole OS path. Prove which layer is active with side-by-side lookups on What Is My IP Address Inquire before you trust a “connected” icon.
Three layers people collapse into one word
“I’m proxied” might mean a Chrome extension, a system VPN client, a TOR browser bundle, or a corporate PAC file. Each leaves a different fingerprint on public IP checks. If you only test inside the browser that hosts the extension, you will misreport the IP that Slack, git, or a game launcher uses.
Extension proxies: scope and blind spots
Most extensions intercept browser HTTP(S) requests. They may ignore WebRTC, DNS, or non-browser processes. Some offer “proxy everything in this browser” but still leak via STUN unless you disable WebRTC or force extension handling.
Symptoms:
- IP inquire page shows exit node A
curlfrom a terminal shows ISP address B- Another browser without the extension also shows B
That pattern is normal for extension-only setups—not a failed VPN install.
System VPNs flip the default route
When a VPN client owns the default route (full tunnel), browsers and terminals usually agree on egress. Split tunnel exceptions still apply, but the disagreement is route-based, not “Chrome versus world.”
If the VPN is connected yet the browser disagrees with curl, suspect an extension overriding the VPN for web traffic—a surprisingly common double-wrap.
The reverse case is equally common and less intuitive: an extension that was installed months ago and forgotten keeps overriding a correctly configured VPN. Users describe the VPN as broken when it is working exactly as configured, and the forgotten extension is doing precisely what it was told to do.
A four-probe method that settles arguments
- All privacy tools off → baseline ISP IP
- Extension on, VPN off → browser IP only
- Extension off, VPN on → browser + terminal IP
- Both on → detect which layer wins in the browser
Record IPv4 and IPv6 each time. Extensions sometimes cover one family.
WebRTC and DNS as silent narrators
Even when the TCP path to an IP website uses the proxy, WebRTC candidate gathering can reveal local or ISP addresses to other sites. DNS may go to the ISP resolver while HTTP rides the proxy, creating policy confusion. For security tests, disable WebRTC in the browser under test or use a hardened profile.
DoH settings can also bypass a VPN’s DNS sinkhole. Note resolver identity when the investigation is about leaks, not just whois of the HTTP egress.
What to tell support (and what not to)
Send the IP that matches the failing client. If the SaaS admin UI is browser-only, the extension’s egress matters. If the API fails from a CI runner, the runner’s egress matters—your laptop extension is irrelevant. Attach probe notes so they do not allowlist the wrong door.
Testing the terminal honestly
Terminal checks are only comparable if they leave through the same stack the application uses. A plain request may honour an environment variable proxy while another tool ignores it, producing two different answers on one machine.
Check which proxy variables are set before you draw conclusions, and test with a second tool if the first result looks surprising. A consistent result across two independent tools is far more informative than a single command’s output.
Corporate images sometimes ship with proxy configuration preloaded. On those machines, an unexpected address is configuration rather than a leak, and treating it as a security incident wastes the afternoon.
Streaming, banking, and geolocation quirks
Services detect more than your exit address. Timezone, language headers, and DNS resolvers all contribute, which is why a proxy that changes the IP can still produce an error page asking you to return to your home country.
That is a detection-layer mismatch, not a broken proxy. Confirming the egress address is the first check, and confirming that the other signals agree is the second.
When a site blocks you despite a correct address, the mismatched signal is usually timezone or locale rather than the exit node. Adjusting those before replacing the tool saves a lot of pointless reinstalling.
Corporate PAC and “automatic proxy”
OS-level automatic proxy configuration affects apps that honor it. Some developer tools ignore PAC entirely. When IP checks disagree across tools, inspect system proxy settings next—not only VPN trays and browser shops.
Settling layer confusion on whatismyipaddressinquire.com
Use the same inquire URL in the extension browser, in a clean browser profile, and cite terminal results beside them. A quick triad on www.whatismyipaddressinquire.com shows whether you are looking at an extension hop, a system VPN egress, or plain ISP paths—before you change firewall rules for the wrong address.


