WebRTC Leak Test
Check whether WebRTC exposes your real IP address, even when you're behind a VPN or proxy. The test runs entirely in your browser.
- Runs in your browser
Why WebRTC can leak
WebRTC discovers your local and public addresses to make peer-to-peer connections work. Behind a VPN, that can reveal your real IP to any website — even when the rest of your traffic is protected.
What we do
Your browser gathers its WebRTC candidate addresses locally, and we compare them with the public IP the server sees. We flag any address that looks like a leak. Nothing about your peers is sent anywhere.
Fixing a leak
If the test finds an address that differs from your VPN’s, disable WebRTC or limit it to the public interface in the browser, use a VPN with WebRTC protection or an extension that controls it, and run the test again.
Frequently asked questions
How do I stop a WebRTC leak?
Use a VPN with WebRTC leak protection, or disable or restrict WebRTC in your browser settings or with a trusted extension.
Is a local IP address a leak?
Local addresses such as 192.168.x.x are not publicly routable. The real concern is a public IP that differs from your VPN or proxy exit.
Does a WebRTC leak affect every browser?
WebRTC is built into Chrome, Edge, Firefox, Safari and Opera. Some browsers hide local addresses with mDNS, but public addresses can still be exposed unless a VPN or a setting prevents it.
Can websites read my address through WebRTC without permission?
Yes, gathering candidate addresses does not need camera or microphone permission. That is why a leak test is worth running whenever you rely on a VPN or proxy.