Why Test DNS Speed
Global averages do not account for your ISP's peering arrangements, your distance to the nearest resolver node, or your local network conditions. The only reliable way to know which DNS resolver is fastest for your specific network is to test it yourself.
A DNS resolver that tests fast from New York might perform poorly from Mumbai. Your ISP's routing to Cloudflare might be excellent while its path to Google is congested. These differences are real and measurable. Running a DNS speed test from your location gives you actionable data instead of generic advice.
Method 1: Online DNS Speed Test Tools
The simplest approach is using a web-based DNS speed test. Our DNS speed test tool sends real DNS-over-HTTPS queries to 17+ public DNS providers simultaneously. The test uses the browser's high-resolution performance.now() API to measure actual response times from your location.
Other online tools include DNSPerf.com for historical performance data, and each major provider's own speed test pages. Online tools are convenient because they require no installation and work from any browser.
When using online tools, run the test at least three times at different times of day for consistent results. Look at the median response time rather than the average, and pay attention to the p95 latency — the worst-case 5 percent of responses.
Method 2: Command Line Testing
For more control, use the dig or nslookup command line tools. Open a terminal and run queries against specific DNS servers to measure response times.
The dig command provides the most detail. Run dig @8.8.8.8 google.com to query Google's DNS. The query time in the output shows how long the lookup took. Repeat this for different resolvers and compare.
The nslookup command is simpler but less detailed. Run nslookup google.com 1.1.1.1 to test Cloudflare. Windows users can also use the built-in DNS diagnostic tools.
For automated testing, write a simple script that queries multiple resolvers in sequence and logs the response times. This gives you precise, repeatable benchmarks.
Method 3: Browser DNS Testing
Modern browsers have built-in DNS testing capabilities. In Chrome, visit chrome://net-internals/#dns to see DNS cache entries and test lookups. In Firefox, go to about:networking#dns for similar functionality.
Browser-based testing reflects how DNS actually performs during real browsing. When you load a webpage, the browser makes dozens of DNS lookups. Testing from the browser captures this real-world behavior.
If you have DNS-over-HTTPS enabled in your browser, the browser's internal DNS test will use the DoH resolver. This gives you the most accurate picture of your actual browsing DNS performance.
What to Measure
The key metrics are median latency, p95 latency, and success rate. Median latency tells you typical performance. P95 latency tells you worst-case behavior. Success rate tells you reliability.
A resolver with 15ms median but 200ms p95 will feel worse than one with 20ms median and 30ms p95. Consistency matters as much as average speed. For gaming and streaming, prioritize the lowest p95 latency.
Also consider consistency across multiple tests. A resolver that gives wildly different results on consecutive tests is less reliable than one with consistent performance. Run at least three tests and compare the variance.
Frequently Asked Questions
How often should I test DNS speed?
Test once when setting up, then retest every few months or if you notice slow browsing. Network conditions change, and your optimal DNS might shift over time.
Should I test from multiple devices?
Yes, if you have different devices. Mobile networks and WiFi might route DNS differently. Test from your most-used device for the most relevant results.