WebRTC Leak Test
WebRTC leak test — check if ICE candidates expose your real IP beyond VPN or proxy.
About this tool
VPNs and proxies mask normal browser traffic, but WebRTC can still leak local LAN addresses or a different public IP through STUN ICE candidates. This test runs entirely in your browser — ICE collection stays local.
What you get
- Pass/fail verdict comparing ICE addresses to your connection IP
- Public and private/local ICE candidate lists
- Candidate types observed (host, srflx, relay)
- Plain-language explanation when a leak is possible
How to use
Click Run test and wait a few seconds. Compare results with VPN or proxy enabled and disabled. Extensions that block WebRTC may show no candidates.
FAQ
What is a WebRTC IP leak?
WebRTC can expose local or public IP addresses through ICE candidates even when VPN or proxy software masks normal browser traffic.
How to test WebRTC leak with VPN connected?
Connect your VPN, run the test, and compare ICE candidates to your expected VPN exit—unexpected ISP or LAN IPs indicate a leak.
How does this WebRTC leak test work?
Your browser collects ICE candidates via STUN—entirely client-side. The tool compares them to your connection IP and flags unexpected addresses.
Can a VPN prevent WebRTC leaks?
Many VPN apps block or route WebRTC. If candidates still show your real ISP IP or LAN addresses, adjust VPN settings or disable WebRTC in the browser.
Is WebRTC leak test safe—does it upload data?
No—the ICE scan runs locally. Only your already-visible connection IP from the page header is used for comparison.
Why do browsers expose local IP via WebRTC?
ICE gathers host and reflexive candidates for peer-to-peer media—those addresses can reveal your LAN or ISP even when the main page traffic uses a VPN.
By using this tool you agree to our Terms of Use and Privacy Policy. Results are provided as-is without warranty.