WebRTC Leak Test
Check whether WebRTC candidate discovery exposes address information in this browser session.
How to interpret the test
Modern browsers may replace local addresses with mDNS hostnames. Compare any detected public address with your expected VPN or network address. No result is a guarantee of anonymity.
How to read this result
Example: a private address, mDNS hostname or VPN-assigned address is not automatically a leak. Compare any public address shown with the main public IP before and after connecting the VPN.
No candidate shown may reflect browser masking or blocked WebRTC. It is not proof that every browser or calling site is safe.
Troubleshooting
- Retry once on the same connection if a provider or browser timeout occurs.
- Repeat on a different browser or network before drawing a conclusion.
- Treat “not detected” or “unsupported” as inconclusive, not proof of privacy or safety.
Example results on this page are labelled examples. Actual results depend on the browser, network, VPN and third-party endpoint availability.
