Proxy Test — Is Your Proxy Working?
docVerify your proxy is working correctly. Detect transparent proxies, SOCKS proxies, and anonymizers.
A proxy is an intermediary that forwards traffic on your behalf, so the destination sees the proxy's exit rather than your direct address. Proxies come in several types that behave very differently: some understand web applications, some pass raw connections along, and some are invisible to the user. Testing a proxy means checking not only the exit address but which side resolves names, what headers are attached, and whether other channels leak the real connection.
Forward proxy versus reverse proxy
The two directions are easy to confuse because both relay connections. A forward proxy sits on the client side: your browser or app sends traffic to it, and it reaches the destination on your behalf. This is the anonymizing or access-routing proxy people mean when they say use a proxy.
A reverse proxy sits on the server side: visitors connect to it, and it distributes requests to backend services behind it. CDNs, load balancers and web gateways commonly work this way. A reverse proxy protects and serves the site; it does not change the visitor's exit. When you test whether a proxy is working, you are checking the forward path only.
HTTP proxy and SOCKS5 compared
| Type | Who resolves DNS | Common leak point |
|---|---|---|
| HTTP proxy | Often the proxy resolves the requested host, because it speaks the web protocol and receives the target in the request line | Headers such as forwarded-for or Via can reveal the origin; non-web traffic is not covered |
| HTTPS proxy with CONNECT | Establishes a tunnel to the target host; the proxy still learns the destination name during setup | Tunnel covers only the configured protocol; DNS in other apps may stay local |
| SOCKS5 proxy | Can hand the host name to the proxy to resolve, or resolve locally depending on client configuration | Configuration-dependent DNS; the proxy adds no application-layer filtering or encryption |
| Transparent proxy | Intercepted by the network; the client did not choose it | Origin address and headers commonly preserved; the user may not know it exists |
The DNS question is decisive for anonymity. If the client resolves the domain locally before handing a raw address to the proxy, your local resolver sees the browsing history even though the web traffic exits through the proxy. A properly configured proxy that accepts host names keeps the lookup on the proxy side.
Transparent proxies, PAC and proxy chains
A transparent proxy is inserted by the network itself, usually by an ISP, a campus or a corporate gateway. Traffic is redirected without the client's explicit setting. Such proxies rarely anonymize: they typically keep source information, logging and policy enforcement.
A PAC file is a script that tells the browser which proxy to use for which destination. It is common on corporate networks: internal hosts go direct, external hosts go through a gateway. Reading the PAC configuration explains why some connections tunnel while others do not.
Proxy chains route traffic through several intermediaries in sequence. Each hop reduces direct contact between client and destination, but each added relay also adds latency and another party that can log or drop traffic. Anonymity levels describe what the destination learns: an elite or high-anonymity proxy hides that a proxy is used and omits origin headers; an anonymous proxy reveals that a proxy is in use but not the original address; a transparent proxy exposes the original address in headers regardless of the relay.
Where proxies leak
- DNS leaks. Local resolution as described above; the destination sees the proxy exit, but the local resolver still recorded the lookup.
- WebRTC. Browser real-time communication can gather local and candidate addresses outside the configured proxy, exposing the real network even when web traffic is proxied.
- Forwarded headers. The proxy may add headers recording the original client address, the proxy name or the hop path. These are readable by the destination.
- Non-proxied applications. Only apps configured to use the proxy follow it. Other programs on the machine connect directly.
How to test a proxy result
- Check the exit address. The detection page should report the proxy's public address, its provider and network type, not your local line. Compare it against a direct connection before proxying.
- Inspect request headers. Look for forwarded-for, Via or similar fields that record the origin or intermediate hops. Their presence indicates the destination can trace part of the path.
- Check the DNS resolver. A DNS leak test should show the proxy-side resolver, not your local ISP. If DNS resolves locally, the proxy is covering web traffic only.
- Test WebRTC and other leaks. Confirm no local or direct candidate address appears. Repeat the check after reconnecting, since some clients only route the active session cleanly.
- Verify coverage. Test the application you actually use. A browser configured for the proxy says nothing about other installed software.
Common misreads
- "My traffic goes through a proxy, so my address is hidden everywhere." The exit hides the web address; DNS, WebRTC and other apps may still expose the local network.
- "A proxy and a VPN do the same job." A proxy usually covers selected applications and adds no encryption by itself; a VPN tunnels system-level traffic and carries its own encryption to the exit.
- "Anonymous in the proxy name means high anonymity." Vendors label services loosely. Judge by the observed headers, resolver and exit type, not the marketing label.
Proxies are a normal tool for remote access, content routing and privacy separation. Using intermediaries to conceal abusive activity, bypass access controls or evade the destination's terms sits under the rules of your jurisdiction and the services involved; relay operators retain logs that can be reached under appropriate process.
Frequently asked questions
Which proxy type should I use for browser privacy?
For a single browser session, a SOCKS5 proxy configured to resolve names on the proxy side, or a VPN covering the whole system, both narrow the visible exit. HTTP proxies remain common for legacy web routing but leave more protocol-specific gaps.
How do I know if I am behind a transparent proxy?
Compare your configured proxy against the observed path: if traffic is relayed though you never set a proxy, and forwarded headers or intercept behavior appear, the network is likely inserting one. Network administrators and ISPs are the usual operators.
Can a proxy hide my fingerprint?
No. It changes the network exit. The browser, screen, fonts, graphics stack and other client readings still report the same device to the destination.