WebRTC Leak Test
Queries the HTTP exit IP through this domain's Cloudflare /cdn-cgi/trace endpoint, then collects WebRTC ICE candidates with stun:stun.cloudflare.com:3478 for comparison.
HTTP Exit IP
--
WebRTC Public IP
--
Parsed from STUN ICE candidates
Local Candidates
Not exposed plainly
No plain local network address was found
STUN Servers
Cloudflare
stun:stun.cloudflare.com:3478
Candidate Details
No candidates yet. Start the test to display results.
About WebRTC leaks
How it works
To create peer-to-peer connections, WebRTC asks STUN servers for network candidates that the browser can use. If those candidates include a public address that differs from the HTTP exit IP, your proxy or VPN may not be handling this traffic.
Why it matters
A leaked public address can reveal your real network exit and let sites infer your actual network location despite a proxy. Plain private, special-use, or reserved addresses can also expose clues about your local network.
How to fix it
Use a VPN or proxy client with WebRTC leak protection, or disable/restrict non-proxied WebRTC UDP in your browser privacy settings or extensions. Retest after changing settings and confirm the WebRTC public IP matches the HTTP exit IP.