WebRTC Leak Test
Check if your real IP address is exposed through WebRTC — even when you're behind a VPN or proxy.
🔓 What Is a WebRTC Leak?
WebRTC is built into every modern browser for video calls and peer-to-peer connections. But it can bypass your VPN and reveal your real IP to any website — a serious privacy risk.
🕵️ Who Can See It?
Any website you visit can use WebRTC to detect your real IP, even if you're connected to a VPN. Trackers, advertisers, and geo-restrictions can all exploit this leak.
🔧 How to Fix It
Use a VPN with built-in WebRTC leak protection, install a WebRTC-blocking browser extension, or disable WebRTC in your browser settings (about:config in Firefox).
WebRTC Leak Test — FAQ
What browsers support WebRTC?
Chrome, Firefox, Safari, Edge, Brave, and Opera all support WebRTC. Safari has partial protection — it exposes local IPs but not public IPs in some configurations. Firefox allows full WebRTC disable via about:config.
Does this test store my IP?
No. The test runs entirely on your device using the WebRTC API. No data is sent to any server. Your detected IPs are displayed only on your screen and disappear when you close the page.
What's the difference between public and local IP?
Your public IP is assigned by your ISP and visible to the internet. Your local IP (like 192.168.x.x) is only visible on your home network. A local IP leak is less serious but can still be used for fingerprinting. A public IP leak through WebRTC completely defeats your VPN.
Can WebRTC be disabled completely?
Yes. Firefox lets you disable WebRTC entirely in about:config by setting media.peerconnection.enabled to false. Chrome and Edge require extensions. Brave blocks WebRTC leaks by default. Safari restricts WebRTC in certain ways automatically.
Why do my detected addresses show .local hostnames instead of IPs?
Modern Chrome and Firefox versions obfuscate local IP addresses using mDNS (multicast DNS). ICE candidates then appear as hostnames like 5f3c2a1b.local instead of raw private IPs. This is a deliberate privacy feature: websites get the obfuscated name, not your real network address, so a .local result usually means the browser is doing its job.
Can WebRTC leak my IPv6 address?
Yes. If your device has an IPv6 address and the browser includes it in ICE candidates, it shows up in the results just like IPv4. An IPv6 leak can reveal your approximate location just as accurately, so check both address families when you review the IP list.
Does incognito or private browsing mode prevent WebRTC leaks?
No. Private browsing hides your history and cookies, not your network interfaces. WebRTC behaves identically in incognito mode, so your real IP will still leak unless you disable WebRTC, block it with an extension, or use a browser with built-in leak protection.
What does a "Partial Leak Detected" result mean?
It means WebRTC exposed one or more public IPs that do not match your current public IP — for example a previous VPN server's address or a carrier-grade NAT address. Your real IP may not be among the detected addresses, but a partial result is still worth investigating, especially if you recently switched VPN servers.
How to interpret your WebRTC test results
- Connect to your VPN first. The test is only meaningful when it reflects the setup you actually trust. Connect your VPN, wait for the connection to fully establish, and only then press Start Test.
- Compare the detected IPs with your public IP. The result box shows your public IP (looked up from a server) and every IP WebRTC exposed. If your real IP appears in the WebRTC list, you have a leak — that means websites can see your true address despite the VPN.
- Expect private addresses or .local names. Seeing 192.168.x.x or an obfuscated .local hostname is normal and only reveals your local network, which is far less sensitive. Focus on public IPs that do not belong to your VPN.
- Re-test after setting up protection. Enable your VPN's kill switch and leak protection, install a WebRTC-blocking extension, or disable WebRTC in your browser, then run the test again. The goal is a result where no public address other than your VPN's appears.
- Repeat on a different network. Leaks can behave differently on home, mobile, and public Wi-Fi networks, especially with IPv6 enabled on one and not the other. Test once per network you regularly use.
Why WebRTC leaks happen even behind a VPN
WebRTC handles real-time audio, video, and peer-to-peer data, and to do that it must discover the most efficient network path between two browsers. It asks your operating system for every local interface — Wi-Fi, Ethernet, mobile data, and even the tunnel created by your VPN — and then sends STUN bind requests to public STUN servers to learn the public address of each one. Those requests bypass the browser's normal proxy and VPN routing in some configurations, which is how your true ISP address leaks out alongside the VPN address.
Browser makers have pushed back. Modern Chrome and Firefox use mDNS to hide local addresses behind obfuscated .local hostnames, which closes the local-IP part of the leak. But public-IP leaks via STUN are only fully prevented when the browser refuses to use non-proxied interfaces, when a hardened browser like Brave filters candidates by default, or when the user disables WebRTC entirely.
That is why a VPN alone is not always enough: many VPN clients only protect normal browser traffic and leave WebRTC's STUN traffic unguarded. The reliable combination is a VPN with a kill switch and leak protection, plus a browser or extension that blocks WebRTC, plus a periodic check with this tool to verify nothing slipped through.