free tool
WebRTC leak test
Check whether WebRTC gives away your real IP address while you browse through a proxy or VPN.
- free
- no account
- runs in your browser
How it works
Why WebRTC can leak.
WebRTC lets a browser make calls and share files directly with another device. To find a route, it asks a STUN server for its public address, and that request goes out over UDP, around the HTTP proxy your browser uses for pages.
So a site can see one address through the proxy and another through WebRTC: your real one. This test makes the same request in your browser and compares the answer with the address our server sees.
If WebRTC shows another public address, it leaks, even one on your own provider's network. The IPv6 side of the same connection is not a leak.
- Antidetect browsers replace the WebRTC address with the proxy's: set it in the profile.
- Firefox: open
about:configand setmedia.peerconnection.enabledto false. - Chrome and Edge: an extension that limits WebRTC to proxied connections.
- A VPN that routes all traffic sends WebRTC through the tunnel too.
Questions
WebRTC can tell a website your public IP even when your pages load through a proxy or VPN, because its address lookup goes around the proxy. When that address is your real one, it leaks.
No. Without a proxy or VPN, the address WebRTC shows is the one sites see anyway. The test matters when you are hiding your IP.
Modern browsers hide your local network address behind a random name ending in .local, so sites cannot read it. When the test lists local addresses instead, your browser shares them: that helps fingerprinting, but it does not reveal your public IP.
It runs in your browser. Your browser asks Cloudflare's public STUN server for its address, the way a video call does, and Google's only if Cloudflare's gives no answer. Our server looks up the network of each address shown. Nothing is saved.
In an antidetect browser, set WebRTC to use the proxy's address in the profile. In Firefox, set media.peerconnection.enabled to false in about:config. In Chrome and Edge, use an extension that limits WebRTC to proxied connections. A VPN that routes all traffic covers WebRTC too.
No proxy can: WebRTC runs inside your browser and picks its own route. Pair the proxy with an antidetect browser or the settings above, then run this test again.
More tools