WebRTC Leak Test

WebRTC lets browsers talk to each other directly for video calls and screen sharing. The catch: while negotiating those connections, it can reveal your IP addresses to any website that asks, sometimes bypassing your VPN. This test shows exactly what your browser exposes through WebRTC. It runs entirely on your device: nothing is sent to our servers.

What is WebRTC?

WebRTC (Web Real-Time Communication) is the browser technology behind video calls, voice chat, and screen sharing on sites like Google Meet, Discord, or WhatsApp Web. It lets two browsers exchange audio, video, and data directly, without routing everything through a server. That direct path is exactly why it needs to discover your real network addresses.

How can WebRTC leak my IP address?

To connect two devices directly, WebRTC asks a STUN server "what is my public address?" and shares the answer (called an ICE candidate) with the web page. Any script on any website can trigger this process silently: no call, no permission prompt, nothing visible. The catch is that some configurations send STUN requests outside the VPN tunnel. Your browser then hands websites your real public IP while your regular traffic shows the VPN address. That mismatch is the leak this test detects.

How to prevent WebRTC leaks

If the test found a leak, you have three solid options. First, use a VPN with built-in WebRTC leak protection and IPv6 tunneling; reputable providers block or rewrite STUN traffic. Second, harden the browser: Firefox lets you disable WebRTC entirely (media.peerconnection.enabled in about:config), Brave ships a WebRTC policy setting, and extensions like uBlock Origin can stop WebRTC from revealing local addresses. Third, disable WebRTC only if you never use browser-based calls, because it breaks Meet, Discord, and similar services. After any change, run this test again to confirm the fix.

Frequently asked questions

Should I disable WebRTC completely?

Only if you never use video calls or screen sharing in the browser. Disabling WebRTC breaks Google Meet, Discord, WhatsApp Web, and similar services. For most people, a VPN with WebRTC protection or a browser that hides local addresses is a better trade-off.

Does a VPN automatically stop WebRTC leaks?

Not always. A VPN replaces the IP that websites see over HTTP, but WebRTC discovery can route around poorly configured tunnels, especially over IPv6. Good VPN clients explicitly block WebRTC leaks, and this page is the quickest way to check that yours actually does.

Why do I see .local addresses instead of real ones?

Modern browsers replace your private LAN addresses with random mDNS names ending in .local. Websites can still establish calls, but they no longer learn your real local IP. It's a privacy protection, and seeing those names means it's working.