WebRTC ICE candidates
WebRTC leak test
WebRTC can learn extra addresses while finding a path for calls. The working check is below; run the privacy test to inspect ICE candidates in this browser.
Affiliate link — we may earn a commission.
Public IP
This lookup runs in your browser so the address is yours, not the address of our hosting server.
Looking up your public IP from your browser…
Privacy score
IdleRun the privacy test to calculate a score.
WebRTC leak test
This test creates a local WebRTC connection to a public STUN server and inspects ICE candidates in your browser. It does not send those addresses to our server.
Run the privacy test to calculate a score.
Session report
Copy a plain-text summary for yourself. Your raw IP is never placed in a public share URL — this app does not create share links.
What this tool does not do
- It cannot prove that a VPN, proxy, or Tor is in use.
- It does not test DNS leaks or malware. A visible public IPv6 address is not a VPN leak by itself.
- It is not a security audit, legal advice, or a guarantee of privacy.
- Location fields are only shown when a free lookup provider actually returns them.
When this test reports a possible leak
A classic story is that ordinary HTTPS goes through a tunnel, but WebRTC still publishes another public address. This page only supports that story when the evidence is there: a public ICE address that does not match the regular IP lookup.
Local addresses such as 192.168.x.x, 10.x.x.x, or fe80:: are how home and office networks work. They are not treated as a confirmed security leak. Hostnames ending in .local are usually mDNS hiding, not a failure.
What WebRTC cannot tell you
This check does not prove a VPN is on or off, and it does not test DNS. ICE candidates stay in your browser; they are not uploaded to this site’s server.
Related guide
A written walkthrough for the situation this tool is often used to check.
Other local checks
These pages reuse the same browser-side checks. None of them can prove that a VPN is enabled.