WebRTC Leak Test: Check If Your Browser Is Exposing Your IP

Ready to test

Click "Run Test", it takes a couple of seconds.

How to read the result

If you're not connected to a VPN, seeing your normal public IP here is expected, that's normal.

If you are connected to a VPN and see an IP address here that's different from your VPN server's IP, that's a WebRTC leak: websites can learn your real address around the tunnel.

Modern versions of Chrome and Edge hide local IPs behind mDNS by default (you'll see something like xxxxxxxx-xxxx….local instead of a real address), that's normal and not a leak. Firefox and Safari behave a bit differently, so it's worth testing in whichever browser you actually use with your VPN.

Found a leak?

404 VPN encrypts your traffic and hides your real IP from the sites you visit. If WebRTC still exposes your address, that's a browser or client setting, not a sign that the VPN itself isn't working.

How to connect 404 VPN →

Frequently Asked Questions

guest@404vpn:~$ cat webrtc-faq.md

[01] $ What is a WebRTC leak? ▸

> WebRTC is a browser technology for video calls and peer-to-peer connections. To connect two users directly, it can expose IP addresses around a configured VPN or proxy.

[02] $ My VPN is on, but the test shows a public IP, is that a bug? ▸

> Not necessarily a bug in the VPN, it's more often a browser or client setting. See "How to read the result" above and the How It Works page.

[03] $ How do I fix a WebRTC leak? ▸

> Most modern browsers let you enable IP-leak protection in their privacy settings, or you can use an extension that blocks WebRTC entirely if you don't need it.

[04] $ Does this test send my data anywhere? ▸

> No: all the ICE candidate analysis happens in your browser. We use a public Google STUN server only to gather the candidate list, the same way any video-calling site does.