Toolsky

Free Online Tools & Utilities for Every Task.

DNS Leak Tester

Check if your DNS queries are leaking and identifying your true location.

Detect DNS exposure and verify VPN tunnel integrity.
Analyzing DNS Queries...

You did everything right: installed the VPN, connected to a server in another country, and checked that your IP address changed. Yet your internet provider may still know every site you visit — because of a DNS leak. The DNS Leak Tester on ToolSky checks whether your DNS queries are escaping your VPN tunnel and identifying your true location, so you can verify that your privacy setup actually works instead of merely assuming it does.

What a DNS Leak Is, in Plain Terms

Every time you visit a website, your device first asks a DNS resolver for directions: "what is the numeric address of this domain?" That question is normally answered by your internet provider's DNS servers, which means your provider can log the domains you look up even though the traffic itself travels through a VPN. A DNS leak happens when those lookup questions slip outside the encrypted VPN tunnel and go to your ISP's resolvers (or another unintended resolver) instead of the VPN provider's. The result: websites see your VPN IP, but your ISP sees your browsing trail, and some services can infer your real location from the resolver's location.

A leak test works by making your browser perform a series of fresh DNS lookups for unique test domains and then reporting which resolver servers actually answered them. If the resolvers belong to your VPN provider, you are fine. If they belong to your home ISP — especially resolvers located in your real town or country while your VPN claims you are elsewhere — you have a leak worth fixing.

What the Test Shows You

  • The DNS resolvers handling your queries: the servers that answered, identified by operator and location where possible.
  • A leak verdict in context: whether the resolvers match your VPN provider or expose your ISP instead.
  • Location clues: resolver geography that can contradict your VPN's apparent location.
  • A repeatable check: run it before and after changing VPN or router settings to confirm a fix worked.

DNS is only one of several browser-level exposures. For a fuller privacy check-up, pair this test with the WebRTC Leak Test, which looks for IP leaks through a completely different browser feature, and confirm your visible address with What's My IP.

How to Run a DNS Leak Test Properly

  1. Connect to your VPN first, choosing the server location you actually use day to day.
  2. Open the DNS Leak Tester page while the VPN is active.
  3. Start the test and wait while it triggers lookups and collects the answering resolvers.
  4. Read the list of DNS servers shown: note their operators and countries.
  5. Compare them with expectations — resolvers should belong to your VPN provider (or a privacy resolver you deliberately configured), not your home ISP.
  6. Disconnect the VPN and run the test again; the resolvers should change to your normal ones, proving the test is measuring the VPN state and not just showing static data.
  7. If you found a leak, apply a fix (see below) and re-test until the ISP resolvers disappear while connected.

What People Discover With This Test

A common story: a remote worker connects to a company-approved VPN in the Netherlands, confirms a Dutch IP, but the test reveals DNS resolvers from their home ISP in their actual country — the VPN app was set to "split tunnelling" or had its DNS setting left on automatic, quietly sending lookups to the router at home. Another frequent discovery involves smart TVs and routers: a user sets a VPN on the router for the whole house, yet the test shows a public resolver nobody recognises, which turns out to be a hard-coded fallback in the router's firmware. In both cases the leak was invisible in everyday use; only a deliberate test exposed it.

Fixing a Leak and Avoiding False Alarms

Start with the VPN app's own DNS setting. Most leaks are configuration issues: look for an option to use the VPN provider's DNS servers, block outside DNS, or enable a kill switch, and turn it on.

Check the router. If the VPN runs on your router, its DNS settings govern the whole network. Manually set the router's DNS to your VPN provider's resolvers or a trusted public resolver, and disable any "DNS relay" fallback that points back to the ISP.

Do not panic over unfamiliar names. A resolver you do not recognise is not automatically a leak: large VPNs use third-party or white-label resolver infrastructure, and privacy resolvers like those from Cloudflare or Quad9 appear legitimately if you configured them. The red flag is specifically your home ISP's resolvers or resolvers in your real location that you did not choose.

Remember browsers have their own DNS. Modern browsers may use DNS-over-HTTPS to a built-in provider, bypassing system settings. That can show up in results and can be adjusted in the browser's privacy settings if you want all queries inside the tunnel.

A pass is a snapshot, not a guarantee. Software updates and network changes can reintroduce leaks, so re-run the test after changing VPN apps, routers, or operating systems. Deeper browser exposure can also be reviewed with the Browser Fingerprint Audit.

Frequently Asked Questions

What exactly leaks in a DNS leak?

The domains you look up, and the identity/location of the resolver answering you. The content of your traffic stays inside the VPN, but the list of sites you visit can be visible to your ISP, which defeats much of the point of using a VPN for privacy.

How can my IP be hidden but my DNS still leak?

Because they are separate channels. The VPN routes your web traffic through its tunnel, but if DNS queries are configured to go to your router or ISP resolver directly, they travel outside it. Many default setups behave this way until you change the DNS settings.

Which resolvers in the results mean I have a leak?

Resolvers operated by your home internet provider, or located in your real area, appearing while the VPN is connected. VPN-provider resolvers and well-known public resolvers you chose yourself are expected and fine.

Does a DNS leak affect streaming or unblocking?

It can. Some services compare your IP location with your DNS resolver location; a mismatch can make them serve your home country's catalogue or flag the connection, even though your IP looks foreign.

Should I test with the VPN off as well?

Yes — testing both states proves the tool is reading your live configuration. With the VPN off you should see your normal ISP resolvers; with it on, you should see only the VPN's.

Can my router cause a DNS leak even with a good VPN app?

If the VPN runs per-device, the router is not involved. But a router-level VPN, or a router set as the DNS server for your network, can absolutely redirect queries to the ISP if its own DNS fields still point there.

How often should I run a DNS leak test?

Whenever your setup changes: new VPN provider, new router, major app update, or switching from app-based to router-based VPN. A ten-second check after each change keeps silent leaks from persisting for months.

Trust, but Verify Your VPN

A VPN's job is to keep both your traffic and your lookups private, and the second half fails silently surprisingly often. Run the DNS Leak Tester with your VPN connected, read which resolvers answer, and you will know — rather than hope — that your location is not leaking through the side door.