WebRTC Leak Test
WebRTC can expose your real IP address around a VPN. The test runs right in your browser — nothing is sent to third-party servers other than Google's public STUN server, standard for this technology.
Browser IP (from a regular HTTP request to the server)
detecting…
IPs detected via WebRTC/STUN
Searching…
Still collecting data…
How to use it: turn on your VPN, wait for it to connect, then refresh this page and compare the addresses. If both match each other but do NOT match your real (non-VPN) IP, WebRTC isn't exposing you. If the WebRTC IP differs from your VPN's address, that's a leak.
Frequently asked questions
What's a WebRTC leak?
WebRTC is a technology for video calls and P2P connections right in the browser. To set up a connection, it can expose your real public IP address via the STUN protocol, even if all your browser's other traffic goes through a VPN.
How do I protect against a WebRTC leak?
Some VPN apps block this kind of leak themselves. You can also disable WebRTC in your browser (in Firefox, via about:config, the media.peerconnection.enabled flag) or use a WebRTC-blocking extension.
Why doesn't the test find anything even though my VPN is off?
Some browsers and network configurations don't expose a public IP via WebRTC at all (due to firewall settings or STUN being blocked, for example) — no result here doesn't always mean there's no leak in other scenarios.