Privacy tool

DNS leak test

Every site you visit starts with a DNS lookup. This test reveals which resolver actually handled yours — and whether it's the one you expect.

Not wired to a real resolver yet — this shows a sample result so you can see the intended format. See the note at the bottom of this page.

What a DNS leak is

When you use a VPN, your DNS lookups are supposed to travel through the VPN too. A DNS leak happens when they slip out to your provider's resolver instead — so even though your traffic is encrypted, your ISP still sees a list of every domain you visit.

Once wired up, the test will work by making your browser resolve a series of unique hostnames, then checking which resolvers asked our servers about them — if a resolver belonging to your ISP shows up while you're on a VPN, that's a leak. For now, the button above returns a sample result in the same format so you can see what it'll look like.

Frequently asked questions

How do I fix a DNS leak?

Enable your VPN's DNS leak protection if it has one, or set your system to use the VPN's resolvers explicitly. On the browser side, DNS-over-HTTPS to a trusted resolver keeps lookups private even outside a VPN.

Do I have a leak if I'm not using a VPN?

Not in the usual sense — without a VPN your ISP's resolver handling your lookups is simply the default. The concept matters once you're using a VPN and expecting your lookups to be private.

Coming soon. A real test needs independent resolver-facing endpoints on separate hostnames — this page is the shell, and the result below is a demo; the measurement runs server-side once wired up. FAQ ships as FAQPage schema; page carries SoftwareApplication + BreadcrumbList.

← back to myaddress.is