DNS benchmark tool

BBSA

Honorary Master
Joined
Jul 11, 2005
Messages
30,169
Reaction score
28,725
Location
People's Republic of South Africa
I put together a quick tool that tests DNS resolver speeds directly from your browser. It probes Cloudflare, Google, Quad9, OpenDNS, AdGuard, NextDNS, ControlD, CleanBrowsing, and several others, then ranks them by average latency. You can also add your own.

Anyone interested can have a look:

 
makes zero noticeable difference to the human eye .Focus on the loading speed of the website rather then dns.Btw iam using the google dns server which is ranked 8th slowest , and DNS resolution is immediate.
 
Last edited:
makes zero noticeable difference to the human eye .Focus on the loading speed of the website rather then dns.Btw iam using the google dns server which is ranked 8th slowest , and DNS resolution is immediate.
You're right, but some of us geeks like playing with these things :whistling:

@Speedster can comfim.
 
Ive never understood it. So many better places you can check for latency (ie routing). DNS is not something that Ive ever considered. But hey, if some people wanna min max their DNS, why not. A tool like winmtr is a better tool to detect latency issues and see where bottlenecks are.
 
makes zero noticeable difference to the human eye .Focus on the loading speed of the website rather then dns.Btw iam using the google dns server which is ranked 8th slowest , and DNS resolution is immediate.
Some of these come with adblocking which makes a huge difference.
 
A tool like winmtr is a better tool to detect latency issues and see where bottlenecks are.
..also pingplotter.

Heck, even pathping.

DNS is such a weird thing to look at for any sort of lag/delay because once it's in the cache, all requests receive instant response from the cache... as long as it's within TTL
 
..also pingplotter.

Heck, even pathping.

DNS is such a weird thing to look at for any sort of lag/delay because once it's in the cache, all requests receive instant response from the cache... as long as it's within TTL

most likely they lack a under the hood understanding of how networking works
 
Hopefully these geeks has done the tour of duty playing around with locally hosted dns sever setups...
Who the **** hasn't setup their own routing and dns sever by now with caching and fallover?

Jesus we did this **** back in day before there were these fancy routing and smart dns services...
 
..also pingplotter.

Heck, even pathping.

DNS is such a weird thing to look at for any sort of lag/delay because once it's in the cache, all requests receive instant response from the cache... as long as it's within TTL

most likely they lack a under the hood understanding of how networking works

Exactly this. Personally, I set a large cache with a max TTL of 2 weeks, redirect all DNS requests to router with a simple firewall rule, use a static cache of things I want to block in combination with an adlist that updates automatically...

Screenshot 2026-04-28 175101.png
Screenshot 2026-04-28 175239.png
PS, not many matches on my adlist since router firmware was updated on Sunday...
 
Just had a lekker chow and a few glasses of wine, but this thread was still stuck in the back of my mind... If anything, (depending on router) a layered approach will provide the best networking performance. Mangle rules, simple queues, and DNS redirection. Especially for SOHO & SME environments with many devices.

Screenshot 2026-04-28 222848.png
Screenshot 2026-04-28 223211.png
 
Top
Sign up to the MyBroadband newsletter
X