WebRTC leak test
This WebRTC leak test shows every IP address your browser reveals through WebRTC and compares them with the IP your connection uses. If WebRTC exposes an address your VPN should be hiding, that is a WebRTC leak.
What is a WebRTC leak?
WebRTC is a browser feature for video calls, voice chat and file sharing without plugins. To connect two people directly, it asks a STUN server “what is my public IP?” and shares the answer with the website.
That request can travel outside your VPN tunnel, especially with VPN browser extensions and some VPN apps. The website then learns your real IP even though the VPN hides it everywhere else.
How to read the results
- Matches your IP: WebRTC shows the same public IP as your VPN. No leak.
- Hidden local address (mDNS): modern browsers replace your local network address with a random name ending in .local. This is normal and safe.
- Local network: a private address like 192.168.x.x. It does not identify you on the internet but adds to your fingerprint.
- LEAK: a public IP that is different from your VPN IP. This is usually your real IP.
How to prevent a WebRTC leak
- Use your VPN’s desktop app, not just the extension. Apps tunnel all traffic at the system level.
- Turn on WebRTC protection in your VPN’s browser extension if it has one.
- Firefox: type about:config in the address bar and set media.peerconnection.enabled to false.
- Chrome and Edge: install an extension that limits WebRTC, such as Google’s WebRTC Network Limiter or WebRTC Leak Shield.
- Brave: open Settings > Privacy and security > WebRTC IP handling policy and pick “Disable non-proxied UDP”.
- Safari: WebRTC does not leak local addresses by default. Run the test to confirm.
Our WebRTC leak prevention guide explains each step.
Which browsers leak through WebRTC?
WebRTC is built into almost every modern browser, so almost every browser can leak. How much it reveals depends on the browser and its settings.
- Chrome and Edge: hide your local network address behind a random .local name by default, but can still reveal a public IP outside the VPN when the VPN does not cover all traffic.
- Firefox: lets you switch WebRTC off completely in about:config, which removes the risk.
- Brave: has a WebRTC IP handling policy in its settings that can limit what is shared.
- Safari: limits WebRTC more strictly than most browsers, but you should still test it.
- Mobile browsers: follow the same rules as their desktop versions. Test them with the VPN on.
WebRTC leaks and VPN browser extensions
A VPN browser extension is a proxy. It sends web pages through the VPN server, but WebRTC traffic can take a different route and skip the proxy. That is why extensions are the most common cause of WebRTC leaks. Many VPN extensions include a WebRTC protection switch. Turn it on, or use the full VPN app, which tunnels all traffic from your device.
WebRTC leak test vs VPN leak test
This page focuses on WebRTC alone and shows every address WebRTC finds. Our VPN leak test runs the same WebRTC check together with your public IP and IPv6 checks. Use this page when you want to fix a WebRTC problem. Use the full test to check everything at once. To see every address side by side, use the IP leak test.
FAQ
Does a WebRTC leak mean my VPN is broken?
Not always. Your VPN may protect everything except WebRTC in the browser. Fix it with the steps above and test again.
Should I disable WebRTC completely?
Only if you do not use browser-based video calls (Google Meet, Discord in the browser and similar). Limiting WebRTC to the proxied connection is a good middle ground.
Can WebRTC leak my IP on my phone?
Yes. Mobile browsers support WebRTC too. Run this test on your phone with the VPN on.
What other leaks should I check?
Run the full VPN leak test to check IPv6 and your public IP as well.
Is WebRTC itself dangerous?
No. WebRTC powers video calls in the browser and is safe to use. The problem is only that it can reveal IP addresses that a VPN or proxy is meant to hide.
Why do I see a .local address?
Modern browsers replace your local network address with a random name ending in .local. This hides your device’s address on your home network. It is normal and not a leak.