Privacy · free

WebRTC leak test

See whether your browser reveals your real IP address through WebRTC, even behind a VPN or proxy.

Running the test…

The test runs in your browser against public STUN servers; the addresses it finds are not sent to us.

WebRTC lets browsers make direct audio, video and data connections. To find a route, the browser asks a STUN server what its public address is, and a web page can read the answer with a few lines of JavaScript. If your VPN or proxy only covers normal web traffic, that answer can be your real IP address: a WebRTC leak.

The test compares the public addresses WebRTC reveals with the address you browse from. They should be the same. Local addresses are hidden by modern browsers behind a random .local name (mDNS), which is not a leak.

How to fix a leak

Firefox: set media.peerconnection.enabled to false in about:config.
Chrome, Edge, Brave: use the VPN’s own extension or an extension that limits WebRTC to the proxied route; Brave has the option under Privacy, “WebRTC IP handling policy”.
VPN apps: many block WebRTC leaks at system level; test again after connecting.

Then check the rest of what your connection reveals with the DNS leak test, the proxy judge and what is my IP.

What is a WebRTC leak?

A website using WebRTC learns your public IP address from a STUN server. When a VPN or proxy does not route that request, the address it learns is your real one, even though normal page requests go through the VPN.

Is a local IP address a leak?

Not by itself. Modern browsers replace local addresses with a random .local name. A private address such as 192.168.1.10 is only visible to your own network and does not identify you on the internet.

Does this test send my addresses anywhere?

No. The candidates are gathered and compared in your browser. Only the normal lookup of the address you browse from goes to our geolocation API.

More tools