Run a WebRTC leak test after you start it. Compare browser-observable public IP candidates with this site's IPv4 and IPv6 exits; a difference alone is not proof of an IP leak.
Detect browser-observable WebRTC public exits and compare each address family with this site's matching exit.
After you start, this page contacts 15 reviewed STUN nodes. Public exits are shown in full. Results are not saved.
Start a check to view WebRTC exits.
Waiting to check
This WebRTC leak test reads browser-observable public candidates and compares them with this site's IPv4 and IPv6 exits. A difference is not automatically a privacy leak; interpret it by address family and network path.
The site exit comes from an HTTP request. WebRTC candidates are observed while the browser reaches reviewed STUN endpoints. Proxy software, browser policy, and dual-stack routing can make them differ, and one address difference alone does not prove an IP leak.
Compare IPv4 only with IPv4 and IPv6 only with IPv6. When a device has both address families, addresses from different families are not a conflict.
First confirm that the difference is stable within one address family, then review IPv4 and IPv6 proxy coverage and routing rules. The check starts only after user action and does not turn node count or an address difference into a proxy, data-center, or account-risk conclusion.
