WebRTC leak test

What this test can and can’t detect

This test runs entirely in your browser and doesn’t contact any third-party STUN server. It collects only host and .local (mDNS) candidates, so it detects whether your browser exposes local network addresses. It cannot detect a public IP address leaked through a STUN server, which some sites use; to limit that, use the browser settings below.

What is a WebRTC leak?

When a page creates a WebRTC connection, the browser lists the addresses it could be reached at, called ICE candidates. Older browsers handed out real local addresses like 192.168.1.20 to any page. Modern Chrome, Edge, Firefox and Safari replace them with random .local names unless you grant camera or microphone access, which is why most people see the safe result.

How to limit WebRTC exposure

• Firefox: open about:config and set media.peerconnection.ice.default_address_only to true, or set media.peerconnection.enabled to false to switch WebRTC off completely (video calls in the browser will stop working).
• Chrome and Edge: keep the browser up to date so local addresses stay hidden behind .local names. Organisations can set the WebRtcIPHandling policy to restrict which addresses WebRTC may use.
• Safari: local addresses are hidden by default. Only grant camera and microphone access to sites you trust.
• Brave: open Settings, then Privacy and security, and set WebRTC IP handling policy to Disable non-proxied UDP.
• Use a VPN on the whole device: with the VPNRice app connected, the public address WebRTC can see is the VPN server’s.