IPCanary

WebRTC Leak Test — see every address your browser will hand out

Open a real peer connection, enumerate every ICE candidate, and compare them against the address you are actually connecting from. Detects VPN bypass in the browser.

Advertisement
WebRTC candidate exposure running
Opening a peer connection against two public STUN servers and enumerating candidates...
Address seen by our edge
216.73.216.227
Network operator
Anthropic, PBC
Autonomous system
AS16509
The test opens an RTCPeerConnection against stun.cloudflare.com and stun.l.google.com, collects candidates for 2.6 seconds, then closes it. Server-reflexive candidates reveal the public address your machine reaches STUN from. If that differs from the address above, something is routing WebRTC around your VPN. Host candidates ending in .local are mDNS-obfuscated, which is the correct modern behaviour and not a leak.

Read: how WebRTC leaks actually happen

Advertisement

Frequently asked

Does a private 192.168 address count as a leak?

Not a public one. It reveals your LAN structure to any page you visit, which is a real if minor privacy issue, but it does not identify you on the internet. Modern browsers obfuscate these behind mDNS hostnames by default.

Why does the test show no candidates at all?

Either WebRTC is disabled by an extension or enterprise policy, or your network blocks UDP to STUN servers. Both prevent leaks, and both also break video calling.

My VPN says it has WebRTC protection. Why do I still see my real address?

Many VPN browser extensions only set the WebRTC IP handling policy for the browser they are installed in. A different browser, or the VPN app alone without the extension, often leaves the leak path open.

Advertisement