WebRTC Leak Test
Check which IP addresses your browser exposes through WebRTC.
Looks up live data Runs in your browser but contacts a public STUN server (Google) to learn your public address.
This test runs in your browser. Your browser contacts a public STUN server (stun.l.google.com) to learn its public address, exactly as a website using WebRTC could. It reveals the IP addresses WebRTC exposes to websites.
About this tool
WebRTC lets browsers connect directly for calls and video, and in doing so it can reveal network addresses to a website, sometimes including your real public IP while a VPN is on. Press Run test and the tool opens a temporary WebRTC connection, gathers the address candidates your browser produces and lists them, labeling each as local (private range) or public. The analysis runs in your browser. To find your public address the browser contacts a public STUN server run by Google, which is how WebRTC normally works. If the list shows a public IP that is not your VPN's, that is a leak.
How to use it
- Connect to your VPN first if you want to test it.
- Press Run test.
- Compare any public address listed with the one your VPN gives you.
- If it differs, disable WebRTC or use a browser setting or extension that restricts it.
Common problems
- The test shows no addresses
- Your browser may block or mask WebRTC addresses, which is a good result. Modern browsers often hide local IPs behind random names.
- A public IP appears while on a VPN
- If it is your real address, WebRTC is leaking it. Adjust your browser or VPN settings and test again.
- The test reports WebRTC as unavailable
- The browser has it turned off or removed, so there is nothing to leak.
- Result says the address was masked with a .local name
- Modern browsers replace your local address with a random mDNS name to prevent exactly this leak. That is the protected outcome.