Can You Detect Proxy
Can websites detect proxies?
Checking…
Simulates what a normal website can learn from your browser — not a stealth audit.
How to use
- Open behind your proxy, VPN, or Tor browser and click Refresh.
- Read ISP/org lines and whether HTTP and WebRTC public IPs disagree.
- Compare with proxy off on the same network for a baseline.
FAQ
Can websites see my proxy settings?
Not your local proxy configuration UI. They see the **egress IP** and **ISP classification** your traffic arrives from — often a datacenter, Tor exit, or anonymizer ASN in geo databases.
How is this different from Can You Detect VPN?
Overlapping signals, different emphasis: [can you detect VPN](/tools/detect-vpn) targets VPN heuristics. This page widens keyword matching to proxy, Tor, SOCKS, and generic anonymizer language in ISP/org fields.
Does Tor always show Yes?
Tor exit nodes often appear as known hosting or anonymizer networks — frequently **Yes** or **Uncertain**, but geo DB accuracy varies. Tor Browser also reduces some fingerprint surfaces separately.
Why Uncertain?
IP lookup failed, or signals neither strongly suggest nor rule out proxy egress.
Can residential proxies hide?
Residential proxy IPs may look like normal broadband in geo data — **No** here does not prove absence of proxying.
Is my IP logged?
Public IP lookup uses this site's /api/my-ip route like other network tools — for displaying geo/ISP, not for selling proxy detection feeds.
Introduction
Can You Detect Proxy highlights egress IP and ISP classification patterns associated with HTTP proxies, SOCKS relays, Tor exits, and datacenter hosts, plus HTTP vs WebRTC disagreement. Websites never read your proxy PAC file — they see where packets exit to the internet.
Corporate proxies, privacy tools, and scraper infrastructure all change that exit. This page shows what a simple client-side plus geo-ISP heuristic might conclude.
What websites can infer
| Signal | Notes |
|---|---|
| ISP/org keyword match | proxy, Tor, SOCKS, datacenter, hosting, cloud |
| HTTP IP ≠ WebRTC IP | Split routing or leak — sites may infer misconfigured tunnel |
| Datacenter ASN | Common for cloud proxies and VPN POPs |
| Consistent residential ISP | Weak evidence against datacenter proxy (not proof) |
Commercial proxy detection adds latency timing, TLS fingerprints, and header anomalies — beyond this demo.
Yes vs No vs Uncertain
- Yes — proxy/Tor/datacenter or IP-path indicators fired.
- No — HTTP/WebRTC consistent without strong proxy keywords.
- Uncertain — incomplete data or mixed weak signals.
Residential rotating proxies deliberately mimic home ISPs — expect false negatives.
Common use cases
- Tor Browser check — see how exit classification might appear to a site.
- Corporate proxy audit — document egress ISP name for split-tunnel apps.
- Scraper ops — compare datacenter exit vs residential proxy labels.
- Security awareness — show that proxy config ≠ invisible egress.
Best practices
- Compare proxy on vs off with Refresh on the same machine.
- Pair with what is my public IP for raw address context.
- For VPN-specific wording, use can you detect VPN.
- WebRTC bypass of proxies shows up in can you detect WebRTC leak.