What Is a DNS Speed Test?
A DNS speed test measures how quickly different DNS servers answer the lookups your device makes before it can load a website. Every time you open a page, your device first asks a DNS resolver to translate the domain (like github.com) into an IP address. If that resolver is slow, every site feels slow — even on a fast connection.
This tool benchmarks three of the most popular public DNS resolvers — Cloudflare (1.1.1.1), Google Public DNS (8.8.8.8) and Quad9 (9.9.9.9) — directly from your browser, then ranks them by the real response time measured from your location. The fastest resolver for someone in Frankfurt is often not the fastest for someone in Mumbai, so a test run from your own network beats any generic global average.
How This DNS Speed Test Works
Each resolver is tested with several timed DNS-over-HTTPS (DoH) queries to unique, uncached hostnames. We send one warm-up request first (to exclude the initial HTTPS handshake), then run eight timed rounds and record each round-trip time. From those samples we calculate the median, minimum and jitter, and rank the resolvers fastest-first.
Because the measurement travels over HTTPS from your browser, the absolute millisecond values run higher than a raw UDP query from your router would. That's expected — what matters is the relative ranking. And the whole test runs client-side: no domain you look up and no result ever touches DNS Robot's servers.
Warm-up — one untimed query per resolver opens the TLS connection so we measure DNS, not the handshake.
Eight timed rounds — unique random hostnames prevent cached answers from skewing the result.
Median over average — the median ignores one-off network spikes for a stable reading.
Reliability score — the percentage of queries each resolver answered, so a fast-but-flaky resolver is easy to spot.
Advertisement
Why DNS Speed Matters
A single web page can trigger 20–50 DNS lookups — one for the page, then more for images, fonts, analytics, ads and APIs hosted on other domains. If each lookup is 40 ms slower than it needs to be, that delay stacks up on every click.
Switching from a slow ISP resolver to a fast public one typically cuts DNS lookup time from 30–60 ms down to 10–20 ms. You won't get more download bandwidth, but pages will start loading noticeably sooner, apps feel snappier, and time-to-first-byte improves across the board.
Fastest Public DNS Servers (2026)
These are the top free public resolvers — all support encrypted DNS and work on any device or router. The live test above benchmarks Cloudflare, Google and Quad9; AdGuard is also an excellent choice to set manually. Copy any provider's IPs into your settings.
Cloudflare
Speed + privacy1.1.1.1 / 1.0.0.1~11 ms avgGoogle Public DNS
Reliability + reach8.8.8.8 / 8.8.4.4~22 ms avgQuad9
Security (malware block)9.9.9.9 / 149.112.112.112~20 ms avgAdGuard DNS
Ad + tracker blocking94.140.14.14 / 94.140.15.15~25 ms avgAverage latencies are global figures from independent benchmarks; your measured result will differ by location. Cloudflare is the most common winner, but it's worth confirming with the live test above.
Advertisement
How to Change Your DNS to a Faster Server
- 1Change DNS on your router (recommended)
Open your router admin panel (usually 192.168.1.1), find the DNS settings, switch from automatic to manual, and enter the primary and secondary IPs of your fastest resolver. One change covers every device on the network — phones, laptops, TVs and consoles.
- 2Windows 11 / 10
Settings → Network & Internet → your connection → Edit DNS server assignment → Manual → turn on IPv4 → enter the addresses (e.g. 1.1.1.1 and 1.0.0.1) → Save. On Windows 10 you can also use Control Panel → Network adapter properties.
- 3macOS
System Settings → Network → your active connection → Details → DNS → click + to add your new servers, remove the old ones, then click OK and Apply.
- 4iPhone & Android
iPhone: Settings → Wi-Fi → (i) → Configure DNS → Manual → add the servers. Android: Settings → Network & Internet → Private DNS → enter a hostname like one.one.one.one (Cloudflare) or dns.google (Google), which also works on mobile data.
DNS Speed Test vs Ping vs Traceroute
These three tools answer different questions. Use them together: if browsing feels slow, run the DNS speed test first (DNS is the most common and easiest fix), then Ping and Traceroute to investigate the connection itself.
Tips for an Accurate DNS Speed Test
- Run it 2–3 times
A single run can be skewed by a momentary network spike. Average a few runs for a stable reading.
- Close bandwidth-heavy apps
Pause streaming, large downloads and cloud sync so they don't compete with the test for bandwidth.
- Test the network you actually use
Wi-Fi, Ethernet and mobile data can give very different results — benchmark on the one you browse on.
- 0% replied ≠ resolver down
If a resolver shows no response, your network or browser is almost certainly blocking its encrypted DNS endpoint.
- Re-test after switching
Confirm the improvement and verify your device is actually using the new, faster resolver.
Found your fastest resolver? Follow the setup guide to apply it across your whole network.