WebRTC Leak Test

A VPN hides your IP from ordinary web requests, but WebRTC can hand it over through a side door. This test asks your browser to reveal what WebRTC exposes and compares it with the address websites see, then gives a plain verdict.

Running test…
Address sites see (this connection)
—
Public IPs found by WebRTC
—
Local IPs found by WebRTC
—
mDNS names (local address hidden)
—
WebRTC support
—

If you are on a VPN and a public WebRTC address differs from the address sites see, your real IP is leaking.

How the test works

WebRTC finds the best path between two peers by gathering ICE candidates: your local network addresses, the public address as seen by a STUN server, and relay addresses if configured. A web page can read those candidates with JavaScript. This page creates a connection, asks two public STUN servers what address they see, and lists everything WebRTC returns. Separately it reads the address your connection to this page arrived from. If WebRTC shows a public address that the page did not otherwise see, your VPN is not covering WebRTC traffic.

What the results mean

Leak detected means a second public address appeared. On a VPN this is your real ISP address and it defeats the purpose of the VPN for any site that runs this same check. No leak with a local address visible is the normal state for most browsers: the LAN address is not a security problem on its own, but Firefox and Brave can hide it and Chrome replaces it with an mDNS name in most configurations. WebRTC disabled is the safest result, at the cost of browser-based video calls.

Your public address on its own is on the homepage. Everything else your browser reveals is listed in the browser info tool. If you are choosing a VPN, the difference between the address it gives you and your own is explained in public vs private IP addresses.

Frequently asked questions

What is a WebRTC leak?
WebRTC is the browser technology behind video calls and peer-to-peer file transfer. To connect two browsers directly it discovers your network addresses and can reveal them to a web page through JavaScript, even when a VPN is hiding your IP from ordinary requests.
I see a 192.168 or 10.x address. Is that a leak?
That is your private local address. It is a mild privacy signal but it cannot identify you on the internet; millions of people have the same one. The serious leak is when a public address appears that differs from your VPN’s.
What does an mDNS .local address mean?
Modern browsers replace local addresses with random .local names to protect privacy. Seeing one instead of a 192.168 address is good; it means the browser is hiding your LAN address.
How do I stop WebRTC leaks?
In Firefox set media.peerconnection.enabled to false in about:config, or use the uBlock Origin option to prevent WebRTC from leaking local IPs. Chrome has no built-in switch; use the WebRTC Network Limiter extension or a VPN client that blocks it. Brave has a setting under Privacy.
Does the test send my addresses to your server?
The test asks a public STUN server for your address, which is how WebRTC works, and compares it with the address from your connection to this page. We display the results in your browser and do not store them.
Scroll to Top