WebRTC Leak Test

What is a WebRTC leak?

WebRTC is a browser API used for peer-to-peer audio, video, and data — the underlying technology for browser-based video calls. As part of establishing a peer connection, WebRTC enumerates the network interfaces and IP addresses your browser can be reached on, including your real public IP. A site that opens a peer connection (even silently in the background) can read those candidates and learn your real IP, even if you are routing your normal HTTP traffic through a VPN or proxy.

This tool opens a peer connection locally, asks a public STUN server (Google’s) to report what address it sees you coming from, and lists all the IPs WebRTC exposed.

How to read the results

• Public IPs — what other peers would see. If you are on a VPN and these match your VPN provider’s address space, the VPN is doing its job. If they match your real ISP, your VPN is leaking through WebRTC and needs to be fixed.
• Local network addresses — private LAN IPs (192.168.x, 10.x). These are not visible on the public internet. Modern browsers (Chrome, Firefox) often replace these with random .local hostnames as a fingerprint countermeasure.
• IPv6 addresses — some networks expose IPv6 addresses through WebRTC. Many VPNs do not tunnel IPv6, so an IPv6 leak is a common failure mode.

How to fix WebRTC leaks

• Browser-level — Firefox has about:config → media.peerconnection.enabled = false. Chrome has the “WebRTC Network Limiter” extension.
• VPN-level — many reputable VPN clients have a “WebRTC leak protection” toggle that blocks WebRTC traffic outside the tunnel.
• Network-level — route all traffic (including UDP) through the VPN tunnel; disable IPv6 if your VPN does not support it.

This test runs entirely in your browser. No data about the detected IPs is sent to our servers.