WebRTC Leak Test
See which IP addresses your browser shares through WebRTC. Run it with your VPN off and on, then compare.
The test asks Google’s public STUN server (stun.l.google.com) for your public address, the same way a video call does. Results stay on this page; nothing is sent to bushe.co.
How to read your result
The test lists every address your browser handed out while it set up a WebRTC connection. Each one is labeled:
- Public address. The IP the wider internet sees for you, as reported by the STUN server. With a VPN on, this should be your VPN’s address.
- Hidden local address (.local). A random name your browser uses instead of your home or office network address. Sites can’t turn it back into the address, so this is fine.
- Local network address. Your device’s address on your own network, such as 192.168.1.20. It doesn’t show where you are, but it does help sites tell you apart.
- Public IPv6 address. An IPv6 address that can be reached from the internet. If your VPN only covers IPv4, this one can give away your real connection.
Check your VPN in two runs
A single run can’t tell whether the public address belongs to you or to your VPN, because this page never learns which VPN you use. Compare two runs instead:
- Turn your VPN off and click Run the test. The public address is your real one. Note it.
- Turn your VPN on, wait until it says connected, and run the test again.
- If the public address changed, WebRTC is going through your VPN. If your real address shows up again, or a public IPv6 address from step 1 is still there, WebRTC is leaking it.
The page keeps a list of your earlier runs until you leave it, so you can compare them side by side.
How to stop a WebRTC leak
Chrome has no switch to turn WebRTC off in its settings, but an extension can change how Chrome hands out addresses. My free WebRTC Privacy Shield does this in one click. Its Max Privacy level turns off WebRTC traffic that doesn’t go through a proxy, and its Balanced level lets WebRTC use only the connection your computer normally sends traffic through, with no local addresses. Many VPN apps also have a WebRTC protection option in their own browser extension.
In Firefox, you can turn WebRTC off completely: type about:config in the address bar, search for media.peerconnection.enabled, and set it to false. Video calls in the browser won’t work while it is off.
After any change, run this test again to make sure it worked. For the background, see my guides on what a WebRTC leak is and blocking WebRTC without breaking video calls.
Frequently asked questions
What is a WebRTC leak?
WebRTC lets sites set up video calls and other direct connections. To do that, the browser can tell a site which IP addresses it can be reached on. If that list includes your real public IP while you use a VPN, a site can see it. That is a WebRTC leak.
How do I know if the IP it shows is a leak?
Run the test with your VPN off, then again with it on. If the public address changes to your VPN’s address, you’re fine. If your real address still shows with the VPN on, WebRTC is leaking it.
What does a .local address mean?
It is a random name your browser makes up to hide your local network address. Sites see the name, not the address, so it isn’t a leak.
Does this test send my IP anywhere?
Your browser contacts Google’s public STUN server (stun.l.google.com) to learn your public address, the same way a video call does. The results stay on this page. Nothing is sent to bushe.co.
How do I stop a WebRTC leak in Chrome?
Chrome has no setting for it, so use an extension that sets Chrome’s WebRTC policy, such as my free WebRTC Privacy Shield, or turn on WebRTC protection in your VPN’s own extension if it has one. Then run the test again.
Related tools
My free Chrome extension that stops WebRTC from giving out your real IP.