WebRTC Leak Test

This test asks your browser's WebRTC engine to gather connection candidates through a public STUN server and checks whether it reveals a public IP address different from the one this page already sees (216.73.216.243).

What is a WebRTC leak?

WebRTC is the browser technology behind video calls and peer-to-peer connections. To connect two peers directly, the browser collects ICE candidates — the IP addresses it can be reached at — including a public address discovered via a STUN server. The problem: a website's JavaScript can trigger this process silently. If you use a VPN or proxy and WebRTC binds to your real interface instead of the tunnel, the site can learn your real public IP even though normal traffic goes through the VPN. That is a WebRTC leak.

How to read the result

• Matches the page IP: WebRTC only revealed the address this site already sees. If you are on a VPN, that is the VPN's address — no leak.
• Different public IP: potential leak. WebRTC may be bypassing your VPN or proxy tunnel.
• Only local or ".local" mDNS names: modern browsers hide private addresses behind random mDNS hostnames — that is good, not a leak.
• WebRTC blocked: nothing can leak via WebRTC in this browser.

Limitations of this test

This is a best-effort browser test, not proof of safety. It uses one STUN server, cannot test TURN-based paths, and only sees what your current browser exposes — other browsers or apps on the same machine may behave differently. Results can also vary between page loads.

Related checks

Combine this with the VPN test and the IPv6 test (an unexpected IPv6 address is another common VPN leak), and read how to hide your IP for the bigger picture.