WebRTC leak test

WebRTC is the browser feature behind video calls and voice chat. To connect two people directly, it asks a public server which address your connection appears to come from. If your browser sends that request outside your VPN, a website can learn your real IP address even though the VPN hides it everywhere else. That's called a WebRTC leak.

How to read the results

• No leak detected: WebRTC shows the same public address websites already see. If you're on a VPN, that should be the VPN's address.
• Possible leak: WebRTC found a public address that's different from the one websites see. With a VPN on, that's often your real address.
• Local address hidden by your browser: modern browsers replace your local network address with a random name ending in .local. That's normal and safe.

Some connections have both an IPv4 and an IPv6 address. If a "leaked" address is simply your other address version, compare it with the home page, which shows both.

How to fix a WebRTC leak

• Turn on your VPN's leak protection. Most reputable VPN apps include WebRTC or IPv6 leak protection in their settings.
• Firefox: type about:config in the address bar, search for media.peerconnection.enabled, and set it to false. This also turns off video calls in the browser.
• Chrome and Edge: install a WebRTC-limiting extension, or use the WebRTC setting in a content blocker such as uBlock Origin.

Then run this test again. This test uses a public STUN server run by Google to see which address WebRTC reports.