Is your browser betraying your real IP?
Even with an active VPN, WebRTC can reveal your local and public IP through browser APIs. This test detects exposed ICE candidates.
- Observed public IP
- 216.73.217.123
- Local IP (WebRTC)
- —
- ICE candidates
- —
Three steps, no install.
WebRTC probe
The browser opens an RTCPeerConnection to public STUN servers (Google, Cloudflare). We capture all collected ICE candidates.
IP analysis
Each candidate is classified: local IP (10.x, 192.168.x) or public IP. Opaque mDNS IPs are ignored.
Leak verdict
If a public IP different from your VPN exit appears, it's a real leak — a malicious site can read it via JavaScript.
How to read this test
WebRTC is designed to enable peer-to-peer communication in the browser. To work, it tries to discover all your IP addresses, including the ones your VPN is supposed to hide.
Good VPNs block these requests at the system level or via their browser extension. If you see a public IP different from your VPN exit, that is a real leak: any site can read it via JavaScript.
Everything you need to know.
Does the test send anything to your server?
No. The WebRTC probe runs 100% in the browser. No candidate IP is transmitted to our servers. Inspect the network console to verify.
Why do I see a local IP 192.168.x.x?
That's normal: it's your internal local network (your router, your computer). WebRTC discovers all interfaces. Only a public IP different from your VPN exit signals a real leak.
How do I block WebRTC leaks?
Three options: (1) enable WebRTC protection in your VPN client, (2) install its browser extension, (3) as last resort, disable WebRTC in about:config (Firefox) or via uBlock Origin.
Does this page use tracking cookies?
Only self-hosted Umami counts visits (GDPR, anonymous, opt-in via banner). No ad pixels, no third-party cookies.
You've seen the gap. Close it.
30-day money-back guarantee. No card required for tools.