What is a DNS leak?
When you use a VPN, all your internet traffic — including DNS queries — should travel through the VPN's encrypted tunnel. A DNS leak occurs when your device sends DNS queries outside that tunnel, directly to your ISP's DNS servers instead. This means your ISP can see every domain you visit, even though you believe your VPN is protecting you.
DNS (Domain Name System) is the system that translates website names like "google.com" into IP addresses. Every time you visit a website, your device makes a DNS query. If those queries bypass your VPN, they reveal your browsing activity to whoever operates those DNS servers — typically your Internet Service Provider.
A DNS leak does not affect your browsing speed or appearance. Everything looks normal. The only way to detect it is with a test like this one — which is why many VPN users have leaks without ever knowing.
How to read your results
No DNS leak detected means this test found only DNS servers associated with your VPN provider or a privacy-focused DNS service. Your DNS traffic appears to be routing through your VPN tunnel as expected.
Possible DNS leak detected means this test found DNS servers that appear to belong to an ISP rather than a VPN provider. This may indicate that DNS queries are bypassing your VPN tunnel. It does not necessarily mean your connection is compromised — some VPN configurations route DNS differently by design. Check your VPN's DNS leak protection settings to confirm.
Your IP address shown above is the public IP address visible to websites you visit. If your VPN is active, this should show your VPN's exit IP address rather than your real home IP.
How to fix a DNS leak
Step 1 — Enable DNS leak protection. Most modern VPN apps include a DNS leak protection or "DNS leak fix" setting. Open your VPN application, go to Settings or Preferences, and enable it. This forces all DNS traffic through the VPN tunnel.
Step 2 — Use your VPN's DNS servers. In your network settings, manually set your DNS servers to those provided by your VPN service. This prevents your device from falling back to your ISP's DNS when the VPN connection drops or behaves unexpectedly.
Step 3 — Enable the kill switch. A VPN kill switch blocks all internet traffic if the VPN connection drops unexpectedly, preventing any unprotected DNS queries from reaching your ISP.
Step 4 — Test again. After making changes, run this test again to confirm the leak has been resolved. Repeat until you see only your VPN provider's DNS servers in the results.
Step 5 — Consider switching VPN providers. If your current VPN does not offer DNS leak protection or consistently leaks, consider switching to a provider that handles DNS entirely within its own infrastructure.
What DNS servers should I see?
If your VPN is working correctly, the DNS servers listed in your results should belong to your VPN provider — not to your home ISP. For example, if you use NordVPN, you should see NordVPN's DNS servers. If you use Cloudflare's 1.1.1.1 as your DNS, you should see Cloudflare listed.
Seeing your ISP's DNS servers while connected to a VPN is the most common indicator of a DNS leak. Common ISP DNS providers include BT, Comcast, AT&T, Verizon, Virgin Media, and similar regional providers. If you see these while your VPN is active, your DNS traffic is likely not being routed through your VPN.
How to run a DNS leak test with and without your VPN
The easiest way to interpret a result is to compare two runs. First, disconnect your VPN and run the test: this shows the IP address and DNS information your normal connection uses, which usually belong to your ISP. Then connect your VPN and run the test again. If the results look identical to the first run, your DNS requests may not be routed through the VPN. If they change to your VPN provider's servers, the result is consistent with no DNS leak.
Other causes of DNS leaks: IPv6 and browser DNS settings
Some VPNs tunnel only IPv4 traffic. On a network that also supports IPv6, requests can bypass the tunnel unless your VPN handles IPv6 or you turn it off in your network settings. Browser features such as DNS over HTTPS can also send lookups to a resolver chosen in the browser rather than the one your VPN provides, so a result may show a public resolver such as Cloudflare or Google even while your VPN is connected. That is not necessarily a problem; it can simply mean the browser resolves names separately from the rest of your system.
Encrypted DNS (DNS over HTTPS or DNS over TLS) stops your ISP from reading your lookups, but it is worth confirming that the resolver you selected is the one you intend to use. For a full walkthrough, see how to prevent DNS leaks, how to tell if your VPN is actually working, and the VPN privacy guide. IP exposure can happen separately from DNS, so you may also want to run the WebRTC leak test.