Addresses your device exposed
Your exit IP (HTTP)
The address every website sees when your browser connects over HTTP.
- Detected exit IP
- —
- ISP
- —
- Country / City
- —
- Network (ASN)
- —
- Browser
- Chrome 149
- Check status
- Running
HTTP/3 (QUIC)
Checks whether your connection negotiates QUIC over UDP or falls back to TCP.
- Negotiated protocol
- —
WebRTC leak (STUN)
Checks whether WebRTC exposes a different IP than your proxy or VPN over UDP.
Collecting ICE candidates from your browser.
- HTTP IP
- —
- WebRTC IP
- —
- Detected public IP
- —
- Public IPv6
- —
- Local LAN IP
- —
- mDNS candidate
- —
WebRTC verification (TURN)
Confirms the browser-reported address against what our relay server actually observes.
- Browser-reported WebRTC IP
- —
- Server-observed (STUN source)
- —
- Server-observed (UDP relay)
- —
- Server-observed (TCP relay)
- —
How anti-bot systems use these signals
A proxy or VPN only hides you if every channel your browser uses agrees on one address. Detection systems do not just read your exit IP, they cross-check the channels below and flag any that disagree.
- Exit IP: the baseline address every website sees over HTTP. Every other channel is compared against it.
- WebRTC: browsers can reveal your real IP over UDP even when a proxy covers your normal web traffic. A different IP here is a direct leak.
- Server-side check: a site can compare the address your browser reports against the one its own server actually receives. An anti-detect browser that rewrites the address is caught here.
- HTTP/3 (QUIC): QUIC runs over UDP. A connection that cannot carry it and falls back to TCP stands out from the large share of traffic already on HTTP/3.
- Consistency: a real visitor almost always has a working, matching WebRTC address. A fully blocked or missing one is unusual, so it is treated as a signal on its own.
The takeaway is simple: a well-configured proxy binds all of these channels to the same IP. Any channel that shows a different address, or no address at all, makes you easier to detect.