DNS Benchmark Tool — Public Resolver Latency

Recursive resolvers answer questions like which IP hosts www.example.com. Every new domain in a browsing session triggers at least one lookup unless cached locally. Milliseconds of resolver delay add to connection setup before TCP and TLS even start.

Benchmarking compares resolver infrastructure responsiveness for the same query name, isolating resolver choice from authoritative DNS hosting quality.

Our handler uses HTTPS-based DNS queries to each provider endpoint. DoH encrypts DNS on the wire between client and resolver, unlike traditional UDP port 53. Latency includes TLS handshake amortization on cold connections.

Rankings therefore reflect DoH performance specifically. Local stub resolvers or UDP may rank differently on your LAN.

fastest names the resolver with minimum latencyMs among successful probes in that run. Ties are broken by sort order after measurement.

Sub-50 millisecond results usually feel instant for web browsing. Hundreds of milliseconds suggest routing issues or overloaded paths worth investigating on repeat runs.

Supplying your own domain tests resolver performance for a name whose authoritative servers may be geographically distributed differently from the default. Cached answers at the resolver can shorten latency — first-query behavior matters most for cold cache.

Invalid domain input falls back to the default query name so the benchmark still completes.

Pick consistently low latency across multiple runs, not one lucky sample. Consider privacy policy, filtering features, and logging practices beyond speed — this tool measures latency only.

Corporate networks often mandate internal resolvers; benchmark results help compare upstream forwarding options, not override security policy.

Geographic distance, ISP peering, time of day congestion, and temporary resolver maintenance shift numbers. Run benchmarks from the network where DNS will actually be used when possible by repeating tests locally after identifying candidates here.

Our measurements originate from the application server environment, not your browser — use as a relative baseline.

Leak tests reveal which resolver your VPN or browser actually uses. Benchmark ranks public resolver speed independently. Combine both when hardening privacy setup.

Changing OS resolver settings requires admin access; benchmark informs choice but does not apply settings.

Filtered resolvers block malicious domains — speed without filtering may trade security. Some resolvers prioritize privacy with slight latency cost.

Authoritative DNS for your own zones is unrelated — slow benchmarks do not mean your zone hosting is bad.

Log results over a week before switching production forwarders. Note queryDomain in each run for audit consistency.

After network upgrades, re-benchmark — new ISP paths can reorder rankings dramatically.