WebRTC leak test.
Check which network addresses your browser exposes.
Connection findings
- Public addresses
- —
- Local addresses
- Not tested
- Status
- Not tested
| Type | Detected value |
|---|---|
| Run the test to collect connection candidates. | |
Technical details
Run a test to see the details.
Compare the detected addresses with your expected VPN exit IP.
Uses your browser’s WebRTC API and Cloudflare STUN after you start. No camera or microphone is requested. Data handling.
How to read a WebRTC leak test
WebRTC can gather network addresses while preparing browser connections. This test requests a temporary data channel and inspects the candidates returned by your browser through a public STUN service. It does not request camera or microphone media.
If you use a VPN, compare any public candidate with the VPN exit address you expect. The test reports observations; it cannot establish the privacy of every application or every network path.
What does an mDNS name mean?+
Some browsers replace a local IP address with a name ending in .local. This changes what is exposed to the page; it is not a second public IP address.
Does an empty result mean there is no leak?+
An empty public-candidate result is inconclusive. Browser restrictions, unsupported APIs or a blocked STUN connection can prevent collection. Try again after checking your connection settings.