Learn
WebRTC leaks — how your browser can expose an IP
Check whether WebRTC can expose an IP address your VPN was meant to hide.
What it detects
WebRTC is the browser technology behind video calls and peer-to-peer connections. To connect peers it gathers “ICE candidates” — including IP addresses — and historically it could surface your real public or local IP even while a VPN was active, without any special permission.
This check runs entirely in your browser and inspects the candidate addresses WebRTC produces, comparing them against your VPN egress to flag whether an address outside the tunnel is exposed.
Why it matters
A WebRTC leak can hand a website your true IP even when every other signal says the VPN is working — a classic, silent de-anonymisation. Anyone running a VPN specifically to hide their IP should confirm WebRTC is not undermining it.
We never transmit the raw candidate IPs off your device; only a leak / no-leak flag is used for scoring (see the privacy policy).
How to read your result
A “leak” result means WebRTC surfaced an address outside your VPN tunnel — the highest-priority thing to fix. A “no leak” result means only tunnel or relay addresses were seen.
Fixes include disabling WebRTC or restricting it via your browser or an extension, or using a VPN client that blocks WebRTC leaks.
Frequently asked questions
- Does a WebRTC leak show my exact IP?
- It can expose your real public IP and sometimes your local network IP — enough to defeat a VPN’s anonymity for that session.
- Do you send my WebRTC IPs to your server?
- No. The comparison happens in your browser; only a leak / no-leak flag leaves your device, never the raw addresses.
- How do I prevent WebRTC leaks?
- Disable or restrict WebRTC in your browser settings or via an extension, or use a VPN app that explicitly blocks WebRTC leaks at the system level.