Live tool · resolver check

DNS Leak Test

See which DNS resolver actually handles your lookups — and whether your DNS leaks past the VPN to your ISP. A VPN can hide the sites you visit while its DNS still betrays them; this test shows the real path.

Resolver

Who handles your DNS

Your browser asks the resolver to identify itself (a standard whoami lookup) — showing the IP and provider that really handle your DNS, the client network it advertises, and the nameserver that sees the query.

Waiting — nothing runs until you press the button.

    Every request this test makes

    One button, one browser-side call — our server is not in the path:

    • dns.google/resolve?name=whoami.ds.akahelp.net — reports the resolver IP, advertised client network (ECS) and nameserver that handled the lookup

    Nothing else is contacted. Nothing you type on this site is ever sent anywhere — the password tools on oopsmypassword.com are 100% client-side.

    How this works — and how to verify it

    These tests make direct, browser-side calls to three services — speed.cloudflare.com, api.ipify.org and dns.google — and to a public STUN server. Nothing else is contacted. Verify it yourself: open your browser's Network tab, run each test, and compare the request list.

    What a DNS leak means — and how to fix one

    Every site you visit starts with a DNS lookup. If those lookups travel outside the VPN tunnel, your ISP — or whatever resolver receives them — sees your browsing destinations even while the page content itself is encrypted. That is a DNS leak: the traffic is protected, the map of where you go is not.

    Reading the result is simple. The resolver row shows the IP and provider that answered; if it belongs to your VPN provider (or a privacy service the VPN routes through), you are routed correctly. If it belongs to your ISP while the VPN is on, the lookups are escaping. The ECS row is the giveaway for forwarded setups — it shows the client network your resolver advertises upstream — and the NS row shows which authoritative nameserver saw the query.

    Fixing a leak starts with the VPN client: update it, turn on its DNS-leak protection, and prefer its own resolvers. If the leak persists, setting your system or router DNS to a resolver you trust — your VPN's, or a public one like Cloudflare's 1.1.1.1 — closes the escape route, though keeping DNS inside the tunnel is the stronger protection. Re-run this test after every change; it is the only honest way to confirm a fix.

    DNS leak test — common questions

    What is a DNS leak?

    A DNS leak happens when your DNS lookups — the requests that turn domain names into IP addresses — bypass your VPN and go straight to your ISP or another resolver. Websites still load through the tunnel, but someone watching the resolver can see which sites you visit.

    How do I read the resolver, ECS and NS rows?

    The resolver row shows the IP and provider of the service that actually answered the query. ECS shows the client network your resolver advertises to authoritative DNS — your ISP's network here can mean a leak. NS shows which authoritative nameserver saw the lookup. If the resolver belongs to your VPN provider, you are routed correctly.

    What should the result show when a VPN is active?

    The resolver should belong to your VPN provider or a privacy service it routes through — not your ISP. If the resolver's IP and provider match your ISP while the VPN is on, the tunnel is not carrying your DNS. Reconnect, enable the VPN's DNS-leak protection, and run the test again.

    Does this test send my DNS queries to your server?

    No. Your browser queries dns.google directly — Google's public DNS-over-HTTPS service — asking it to report which resolver actually handled the lookup (a standard whoami trick). Our server is not in the path, and only that one host is contacted.

    Can I fix a DNS leak without changing VPN?

    Sometimes. Switching your system or router DNS to a resolver you trust (your VPN's, or a public one like Cloudflare's 1.1.1.1) closes the leak for lookups, but the VPN's own leak protection is the stronger fix because it keeps DNS inside the tunnel. Update the VPN app first — most leaks come from outdated clients.