WebRTC Leak Test
WebRTC — the browser feature behind video calls — can reveal the IP addresses of your device to any website, sometimes even when you're on a VPN. This test asks your own browser what it would expose, right here, without sending anything anywhere.
What the test found
When you press the button, this page opens a local RTCPeerConnection and reads the ICE candidates your browser generates — the same addresses it would offer to a peer during a call. Any address shown here is something a website using WebRTC could potentially see.
Modern browsers increasingly protect you: many now show an mDNS placeholder (a random .local name) instead of your true local IP, and public-IP exposure is rarer than it used to be. Seeing a 192.168.x.x or 10.x.x.x address is a local IP leak; seeing your real public IP here would be a more serious one.
How to reduce WebRTC leaks
- Use a browser or extension that disables or restricts WebRTC.
- Use a VPN or privacy browser that blocks WebRTC leaks specifically.
- Turn WebRTC off entirely if you never make in-browser calls.
Related reading: browser fingerprinting, how to hide your IP address, and what your IP reveals. To see your normal public IP, use What's My IP.
Frequently asked questions
Is my data safe with this test?
Yes. Everything runs locally in your browser via a loopback RTCPeerConnection. No addresses are uploaded — they're only displayed to you on this page.
I use a VPN but I still see an address — is that bad?
If it's a private/local address (192.168.x.x, 10.x.x.x, 172.16–31.x.x), that's your LAN IP and usually low-risk. If it shows your real public IP while your VPN is on, that's a genuine leak worth fixing.
Why did it find nothing?
Your browser may block WebRTC, return only an mDNS .local candidate, or have the feature disabled — all of which are good for privacy.
Want the theory? Read the guides → · Visit the zoo →