WebRTC Leak Test

How the test works

WebRTC is the browser technology behind video calls in Google Meet, Discord and many other apps. To connect two people directly, it asks a STUN server for your public address and lists your local network addresses. Websites can trigger this quietly with a few lines of JavaScript.

This test does the same thing in your browser, then compares the addresses WebRTC exposes with the IP address our server sees for your connection.

What the results mean

How to fix a WebRTC leak

• Turn on leak protection in your VPN app or extension. Most good VPNs include it.
• Firefox: open about:config and set media.peerconnection.enabled to false. This turns WebRTC off completely, which breaks video calls in the browser.
• Chrome, Edge, Brave: install an official WebRTC-control extension, or in Brave go to Settings → Privacy → WebRTC IP handling policy → Disable non-proxied UDP.
• Safari: WebRTC leaks are rare on current versions, which hide local addresses by default.

Run the test again after each change. Learn more in what is a WebRTC leak and check for DNS leaks too.

Frequently asked questions

Does a WebRTC leak happen without a VPN?

Without a VPN, WebRTC shows the same public IP websites already see, so nothing extra leaks. The problem only matters when you rely on a VPN or proxy to hide your address.

Is it safe to disable WebRTC?

Yes, but video and voice calls in the browser will stop working. Leak protection in your VPN is a better option if you use web-based calls.

Why does the test show an IPv6 address?

Your connection supports IPv6. If your VPN only tunnels IPv4, your real IPv6 address may leak. Check the IPv6 row on the home page while connected to your VPN.

Last updated October 20, 2026 by the FindMyIPLocation team.