DNS Speed Test

Time public DNS servers from your connection and see which one is fastest for you.

Free, no sign-up, about 20 seconds. Your browser contacts each DNS service directly, so they see your IP address; nothing is stored here.

  • Cloudflare 1.1.1.1
  • Google 8.8.8.8
  • Quad9 9.9.9.9
  • OpenDNS 208.67.222.222
  • AdGuard 94.140.14.14
  • Control D 76.76.2.0
  • CleanBrowsing 185.228.168.9
  • Your current DNS

Which DNS Server Is the Fastest?

The fastest DNS server is the one with a server closest to you, and that depends on where you are and on your internet provider. This DNS speed test times seven public DNS services and your current DNS from your own connection, then shows the fastest with its addresses.

Big public DNS services use anycast: the same address, such as 1.1.1.1 or 8.8.8.8, is answered by the nearest of many servers around the world. A service with a server in your city answers in a few milliseconds; one whose nearest server is in another country takes longer. That's why a ranking measured somewhere else, even a good one, may not be yours, and why "the fastest DNS near me", a DNS speed test "for my location" or "the fastest DNS in India" can only be answered by testing from where you are.

Speed isn't the only thing to compare. Quad9 and CleanBrowsing block malicious domains, AdGuard blocks ads, OpenDNS blocks phishing; Cloudflare, Google and Control D (free, unfiltered) block nothing. The best DNS servers guide compares their privacy, filtering and features.

How This DNS Speed Test Works

Your browser sends real DNS lookups to each service, six rounds in a new random order, and keeps the median time: one figure for popular names the service has cached, one for new names it must look up.

ColumnWhat is timed
CachedLookups of popular names (google.com, youtube.com, wikipedia.org and others), which every big DNS service keeps in memory. This is what most of your browsing feels like. Below it, the fastest and slowest of the six.
UncachedLookups of new random names under our own test domain. No one asked for them before, so the service must ask our DNS server, in the US East (Virginia). Every service makes the same trip, so the comparison stays fair; from far away, all the times are higher.
First requestThe first lookup, which also opens the connection: finding the service's address, then the TCP and TLS handshakes. Your browser does this once and reuses the connection.
AnsweredLookups that got an answer within 3 seconds. A service that misses more than one in five is ranked last, however fast its other answers were.

Ranking: by the cached time, with a quarter of the uncached time added, because most lookups hit the cache but new names still happen on every page with ads, images or scripts from other sites.

Your current DNS: the browser looks up new names under the same test domain through your system, as any website would, and our DNS server tells which resolver asked (as in the DNS leak test). The time is approximate: it goes through your browser and system, and includes failing the request once the name turns out not to exist.

Cached: for a popular name such as youtube.com the DNS server answers from memory after one round trip. Uncached: for a new name it first asks the root, the .com servers and the domain's own DNS server, up to 3 more round trips

What a browser can't measure: a web page can't send plain DNS (UDP port 53, RFC 1035), only DNS over HTTPS (RFC 8484). So the times above include a short HTTPS step that plain DNS doesn't have, usually a millisecond or two on an open connection, and the same for every service. To time plain DNS, use the commands below. The services you test see your IP address, as they would if you used them.

What Is a Good DNS Response Time?

For cached names, under 20 ms is excellent and under 50 ms is good. Over 100 ms is slow: a closer DNS server would help.

Cached lookupRatingWhat it usually means
under 20 msExcellentA server in your city or your provider's network
20 – 50 msGoodA server in your region; you won't notice the difference
50 – 100 msFairThe nearest server is far away, or busy Wi-Fi adds delay
over 100 msSlowAnother country, a congested link or a VPN; try the faster servers in the table

Uncached lookups always take longer, since the server waits for other DNS servers; in our test they also include the trip to Virginia. Compare them between services rather than with these ratings. A low time matters less than a full "Answered" column: a DNS server that sometimes doesn't answer makes pages hang for seconds.

Does a Faster DNS Make Your Internet Faster?

Only a little: a faster DNS shortens the lookup that starts each new connection, not your download speed, upload speed or ping in games.

What you noticeDoes a faster DNS help?
Opening a site you haven't visited todayYes, by the difference in lookup time, usually a few to a few tens of milliseconds
Pages that hang before they start loadingYes, if your current DNS is slow or misses answers: see DNS server not responding
Download and upload speedNo: measure them with the speed test
Ping and lag in online gamesNo: the game talks to its server without DNS once connected
Video bufferingRarely: many streaming services pick a video server near your DNS server, so a distant DNS server can even make it worse

So switch if your current DNS is clearly slower in the test, misses answers, or you want filtering or encryption; don't expect a faster connection. Latency to the sites themselves matters much more.

How to Test DNS Speed on Your Computer

Time one lookup against one DNS server with a single command; run it twice, because the first answer may be uncached and the second cached. The command for your system is open below.

Windows (PowerShell)
  1. Right-click Start and open Terminal or PowerShell.
  2. Run the command, then again with 8.8.8.8, 9.9.9.9 or your provider's DNS server. It prints the time in milliseconds.
(Measure-Command { Resolve-DnsName example.com -Server 1.1.1.1 -DnsOnly }).TotalMilliseconds

-Server sends the lookup to that DNS server; the time includes a few milliseconds of PowerShell's own work, the same for every server. Your current servers are listed by Get-DnsClientServerAddress.

Mac

Open Terminal and run the command; dig comes with macOS. It prints a line such as ;; Query time: 12 msec.

dig @1.1.1.1 example.com | grep "Query time"

Your current DNS servers: scutil --dns | grep nameserver.

Linux

The same dig command; if it's missing, install dnsutils (Debian, Ubuntu) or bind-utils (Fedora, RHEL).

dig @1.1.1.1 example.com | grep "Query time"

Your current DNS servers: resolvectl status.

Phone (Android, iPhone)

Phones have no built-in DNS command: the test at the top of this page is the simplest way, in your phone's browser. Test once on Wi-Fi and once on mobile data, since each network gives you a different DNS server. The result gives the Android Private DNS hostname of the fastest service.

For a long benchmark of hundreds of DNS servers, plain DNS, DNS over TLS and DNS over HTTPS, GRC's DNS Benchmark (Windows) does it for a one-time $9.95 since version 2; the old free version was withdrawn.

Why DNS Speed Test Results Change

Results move with your Wi-Fi, the time of day and your route to each service; test two or three times, at different hours, before switching.

  • Wi-Fi: a weak or busy Wi-Fi signal adds delay to every lookup. Test close to the router, or on a cable.
  • VPN: with a VPN on, every lookup goes through the VPN server first, so you measure from its country.
  • Mobile data or another network: each network has its own route to each service; the fastest at home may not be the fastest at work.
  • Evening peaks: busy hours on your provider's network slow everything, DNS included.
  • Anycast: a service can send you to a different server from one hour to the next, after routing changes.

Copy the two addresses of the fastest server and set them on your router for every device at home, or on one device.

  1. Follow how to change DNS settings for your router, Windows, Mac, iPhone or Android.
  2. On Android, Private DNS takes a hostname instead, such as one.one.one.one or dns.google, and encrypts your lookups.
  3. Flush the DNS cache, then run this test again: "Your current DNS" should now name the new service.

Frequently Asked Questions

What is the fastest DNS server?
There's no single fastest DNS server for everyone: the fastest is usually the one with a server closest to you. Cloudflare (1.1.1.1), Google (8.8.8.8) and Quad9 (9.9.9.9) answer from many cities and are often at the top, but the order changes from one country, provider and network to the next. The test on this page shows the order from your own connection.
Is Cloudflare 1.1.1.1 faster than Google 8.8.8.8?
Often, but not everywhere, so Cloudflare isn't the fastest DNS for everyone. Both answer cached names in a few milliseconds when one of their servers is near you; where Google has a closer server, 8.8.8.8 wins. Run the test: it times both from your connection, side by side.
How do I test my DNS speed?
Press Start on this page: it times public DNS servers from your browser and your current DNS, then shows the fastest. To test plain DNS from your computer, time a lookup against one server: on Windows, Measure-Command { Resolve-DnsName example.com -Server 1.1.1.1 -DnsOnly } in PowerShell; on Mac and Linux, dig @1.1.1.1 example.com, which prints the query time.
What is a good DNS response time?
For names the server has cached, under 20 ms is excellent, 20 to 50 ms is good, 50 to 100 ms is fair and over 100 ms is slow. Uncached lookups take longer, because the DNS server must ask other servers first.
Will changing DNS make my internet faster?
Only the lookup that starts each connection gets faster, usually by a few milliseconds to a few tens of milliseconds. Your download and upload speed and your ping in games don't change. A fast DNS helps most when your current one is slow or unreliable.
What is the fastest DNS for gaming, PS5 or Xbox?
DNS doesn't change your in-game ping: once a game is connected, it talks to the game server without DNS. A fast, reliable DNS can make store pages and matchmaking start a little sooner. Run this test on the same network as the console, pick the fastest, and set it on the console or the router.
How do I test DNS speed on Wi-Fi?
Run the test on a device connected to that Wi-Fi: the result is for that network. To use the fastest DNS on every device on the Wi-Fi, set it on the router. If the times are much higher than on a cable or close to the router, the Wi-Fi signal is adding delay, not the DNS server.
Is there a DNS speed test app or APK?
You don't need one: this test runs in any phone or computer browser, with nothing to install. On Android, the result also gives the Private DNS hostname of the fastest service, which you set in Settings without an app.
Which Private DNS is fastest on Android?
The one that wins this test on your phone, since Private DNS uses the same servers. The result shows the Private DNS hostname of the fastest service, such as one.one.one.one for Cloudflare or dns.google for Google; OpenDNS has none, because it doesn't offer DNS over TLS. Run the test once on Wi-Fi and once on mobile data.
Is a DNS ping test the same as a DNS speed test?
No. Pinging 1.1.1.1 or 8.8.8.8 measures the network round trip to the server, not how fast it answers a lookup, and ping doesn't test DNS resolution at all. A DNS speed test sends real lookups, so it also counts the time the server takes to find the answer, which matters most for uncached names.
How do I know which DNS server I'm using?
Run the test: "Your current DNS" names the operator of the DNS server that answers your device, for example your internet provider, Cloudflare or AdGuard. Our DNS leak test lists every server it sees, with its network and country.
Can I test my internet provider's DNS?
Yes: the test times your current DNS, which is usually your provider's, and names who runs it. A web page can only reach other DNS servers over DNS over HTTPS, which most providers don't offer, so to compare your provider's server with the others in plain DNS, run the commands on this page with its address.
Is this DNS speed test accurate?
It measures real lookups from your connection, six rounds per server, and shows the median. It uses DNS over HTTPS, so each time includes a short HTTPS step that plain DNS doesn't have; the order between servers is what matters. Results change with Wi-Fi, time of day and VPNs, so test again before deciding.

Next steps

Related Tools

DNS Leak Test
Which DNS servers your browser really uses.
Internet Speed Test
Your download and upload speed and latency.
DNS Lookup
Every DNS record of a domain, from the resolver you pick.
DNS Tools
Every DNS tool, and a one-screen domain health check.

Related Guides

Guide Best DNS Servers
Compare the free public DNS servers.
Guide How to Change DNS
On the router for every device at home, or one device.
Guide What Is DNS?
How a name becomes an IP address.