Why WebRTC can leak your IP
WebRTC powers in-browser calls and file sharing. To establish a direct peer connection it asks a STUN server for your reachable IP addresses. That mechanism can surface your real public IP even when a VPN is connected, because the request may travel outside the VPN tunnel. The result: a site could see your true ISP-assigned address despite your VPN.
How to read the result
- No public IP leaked: good. WebRTC isn't exposing a routable address.
- Public IP exposed: if it's your real (non-VPN) address while connected to a VPN, you have a leak to fix.
- .local addresses: harmless; your browser is masking your local IP with mDNS.
Next steps
Confirm your VPN is active with the VPN check, review what else your browser reveals in Browser Info, and read how to hide your IP.
Frequently asked questions
What is a WebRTC IP leak?
WebRTC is a browser feature for real-time audio and video. To connect peers it can discover your IP addresses, and in some cases that reveals your real public IP even while a VPN is active, bypassing the tunnel.
Why does the test only show a .local address?
Modern browsers replace your real local IP with a random mDNS '.local' hostname to protect privacy. That's expected and safe, and it means your true local IP isn't being exposed.
How do I fix a WebRTC leak?
Use a VPN with built-in WebRTC leak protection, install a browser extension that disables WebRTC, or turn WebRTC off in your browser's settings/flags. Then re-run this test to confirm no public IP appears.
Does this test send my IP anywhere?
No. The detection happens entirely in your browser using WebRTC; we don't transmit or store the discovered addresses.