Localtonet tools

DNS leak test

See the DNS resolver paths observed during a fresh lookup. Compare them with your expected VPN or DNS setup.

Your result

Ready to check your DNS path

Start the test to create a temporary hostname and observe its DNS queries.

Ready
Resolver pathsNot checked
DNS queriesNot checked
ObservationNot started
How it works

DNS resolver observations

Run the check to see the measured values.

Several addresses may belong to the same DNS service. Compare the observed paths with your VPN or secure DNS settings before judging a leak.

How it works Guidance & troubleshooting

Use the result with your DNS settings

DNS turns a website name into an IP address. A DNS leak occurs when those lookups take a route you did not expect, such as bypassing the DNS resolver configured by a VPN.

This test creates a fresh hostname and observes the resolver addresses that query Localtonet's authoritative DNS service. Where available, a reverse DNS name and a local ASN database describe the server's network. A network owner may differ from the DNS service operator. Use the WebRTC leak test separately to check browser-exposed IP addresses.

Check your expected DNS

Review the DNS provider configured by your VPN, browser or network. Those settings define the route you expect.

Several resolver paths

A provider may use multiple servers, and browser or network fallback can add paths. A higher count alone is not proof of a leak.

No observed query

Filtering, delegation delays or an unavailable collector may stop the test. Check again before drawing a conclusion.

Compare network names

Network ownership and reverse DNS names help identify the observed infrastructure. A name alone does not prove which service configured your DNS.

Common questions
What is a DNS leak?

It is DNS traffic using a route or resolver you did not expect, such as traffic bypassing the resolver provided by your VPN.

Does an unfamiliar resolver ID prove a leak?

No. The ID is a pseudonymous egress identifier, not a provider name. It needs an expected baseline before it can support a leak claim.

Can secure DNS in the browser change the result?

Yes. A browser’s encrypted DNS setting can select a resolver independently of your operating system, router or VPN.

Are resolver addresses displayed?

The updated collector returns resolver addresses only to the browser that created the temporary observation. Older collector versions return pseudonymous IDs only.

support