DNS Leak Test
Check whether your VPN is really hiding where your traffic comes from. This browser-based test inspects your exit network and checks for WebRTC address leaks — two of the most common ways a "protected" connection still gives you away.
Nothing runs until you opt in. Starting the test sends one request to an IP lookup service (ipapi.co, ipwho.is, or ipify) and performs a local WebRTC check that never leaves your browser.
What is a DNS leak?
Every time you visit a website, your device asks a DNS server to translate the domain name into an IP address. When you use a VPN, those DNS queries should travel through the encrypted tunnel to the VPN’s own resolvers. A DNS leak happens when queries escape the tunnel and go to your ISP’s resolvers instead — meaning your ISP (and anyone watching that path) still sees every site you visit, even though your traffic looks “hidden.”
What this test can and cannot detect
Browsers deliberately can’t see which DNS resolver your operating system uses, so no purely in-browser test can name your resolver directly. This v1 test checks the two signals a browser can verify honestly:
- Exit network identity: if you’re on a VPN but your home ISP shows up here, your traffic (and almost certainly your DNS) is leaking.
- WebRTC address exposure: WebRTC can reveal local and public addresses that bypass the VPN tunnel entirely.
For a resolver-level check, use the leak-test tool built into your VPN app or your VPN provider’s website — those operate dedicated DNS servers that can observe which resolver actually contacts them.
How to prevent DNS leaks
- Enable your VPN’s built-in DNS leak protection and kill switch.
- Use your VPN provider’s DNS servers rather than your ISP’s defaults.
- Enable DNS-over-HTTPS (Secure DNS) in your browser settings.
- Disable WebRTC, or use a browser extension that limits WebRTC address exposure.