Stop WebRTC leaking your real IP

A WebRTC leak is when your browser gives a website your real public IP address even though a VPN is on. WebRTC, the browser feature behind video calls, asks outside servers which addresses it can be reached on, and some VPN setups let that request go around the tunnel. A system-wide VPN app or one browser setting stops it.

Check for a leak

1. Turn your VPN on.
2. Run the Lag Check and open the privacy and leak section of the result.
3. Read the WebRTC row. It compares the public addresses WebRTC finds with the address our server sees for the same visit.

What the result means

• No leak: WebRTC reports the same public address the site sees, which is your VPN's. Nothing to fix.
• Leaking, with an address listed: that address reached the page outside the VPN. If it is your home address, use the fixes below.
• No WebRTC address found: WebRTC is blocked or switched off in this browser, so it can't leak.

Fix it

• Use your VPN's app, not a browser extension, and turn on its kill switch. System-wide tunnels rarely leak.
• Firefox: open about:config and set media.peerconnection.ice.default_address_only to true. To disable WebRTC entirely, set media.peerconnection.enabled to false (this breaks browser video calls).
• Brave: Settings → Privacy and security → WebRTC IP handling policy → Disable non-proxied UDP.
• Chrome / Edge: install uBlock Origin and enable Prevent WebRTC from leaking local IP addresses in its settings, or use your VPN provider's WebRTC protection.

Then run the Lag Check again and confirm the leak row says "No leak".

What a leak exposes

Your public IP address shows a website roughly where you are, usually to the nearest city, and which provider you use. That is what a VPN is meant to hide, and it is all a WebRTC leak gives away: not your browsing history, your files or your exact address. Without a VPN there is nothing extra to leak, because every site already sees that address.