Theme

Popular tools

DNS Speed Test

Check DNS speed from your own connection: this DNS server test times real lookups from your browser to 12 public resolvers and to your current DNS, shows where each answer came from, and how to switch to the fastest.

Timed in your browser over HTTPS · your current DNS seen by our test nameserver · your results stay in your browser

Runs in your browser · about 16 s · your results stay in your browser

12 public resolvers, ready to timeCached · New nameNew name

  1. Your current DNS

    seen by our test nameserver

    —browser cache
    —

  2. no filtering

    1.1.1.1 · one.one.one.one

  3. no filtering

    8.8.8.8 · dns.google

  4. blocks malware

    9.9.9.9 · dns.quad9.net

  5. Free, unfiltered

    76.76.2.0 · p0.freedns.controld.com

  6. your own filters

    dns.nextdns.io/dns-query

  7. blocks ads & trackers

    94.140.14.14 · dns.adguard-dns.com

  8. blocks phishing

    208.67.222.222

  9. Security filter

    185.228.168.9 · security-filter-dns.cleanbrowsing.org

  10. no filtering

    185.222.222.222 · dot.sb

  11. Unfiltered

    86.54.11.100 · unfiltered.joindns4.eu

  12. blocks child-abuse sites only

    public.dns.iij.jp

  13. Basic

    77.88.8.8 · common.dot.dns.yandex.net

cached lookupsnew names≤ 75 ms≤ 200 msslowerms · log scale

How does this DNS speed test work?

It times three things for every resolver, from your own browser: the first connection, lookups of popular names the resolver has already cached, and lookups of brand-new names it can't have cached. Each lookup is a real DNS query over HTTPS, so the time includes your connection, the trip to the resolver's nearest site and its own work: a DNS latency test from exactly where you are.

Four queries run at a time, in a new random order every round, so a busy moment on your line hits every resolver alike. The median ranks them; one slow answer can't sink a resolver, and a lookup unanswered in 3 seconds counts as a failure, never as a made-up time.

Your current DNS is measured too: your browser looks up names only our test nameserver answers, and our nameserver sees which resolver asked.

  • First connection, once: the resolver's own address lookup, TCP and TLS. Your device keeps the connection open after that, so it isn't counted again.
  • Cached lookup: a popular site the resolver already holds. This is the number that ranks it.
  • New name: a name nobody has asked for, so the resolver must ask the domain's own server first, the way it does for a site you've never visited.

1First connection, once

133 ms

DNS + TCP + TLS

2Cached lookup ×8

58 ms

median · popular names

3New name ×4

60 ms

median · random names

Cloudflare from the recorded run: 133 ms to connect, 58 ms for cached names, 60 ms for new ones.
DNS speed test results: resolvers ranked by cached lookup time, with where each answer came from and your current DNSDNS speed test results: resolvers ranked by cached lookup time, with where each answer came from and your current DNSThe verdictThe fastest resolver whose answers were read and checked, or a tie when two are within 5 ms.Your current DNSThe resolver your device really uses, timed on the same kind of brand-new names as the winner.Every lookupCached lookups as dots, new names as rings, the medians as ticks, on one log scale.Where answers came fromEach site that answered, nearest first, against the fastest any server that far away could answer.
A recorded run from a fibre line in India (the connection's details are made up). Each row: the resolver, where its answers came from, every lookup as a dot, and the medians.

Why is the fastest DNS different for everyone?

Because each resolver answers from whichever of its sites your network reaches, and distance sets a floor. Light in fibre needs about 1 ms per 100 km there and back (ITU-T G.114), before any routing or processing.

In the recorded run the resolvers that answered from India took 58–81 ms, while the sites in Europe and Japan took 197–354 ms. The same resolver can be the fastest in one city and the slowest in another, and it can even change between your Wi-Fi and your mobile data.

That's why this test shows where each answer came from, read from the server's own name for itself (NSID, RFC 5001), not only how long it took.

010020030040002,0004,0006,0008,000light's limit: 1 ms per 100 km there and back58 ms · Chennai63 ms · Navi Mumbai81 ms · Chennai197 ms · London296 ms · Frankfurt354 ms · Frankfurt
Every dot is a resolver from the recorded run. Nothing can sit inside the hatched area; the further a dot is above the line, the more time went to routing and work, not distance.

Cached or new: why does a DNS lookup take longer the first time?

A resolver answers a name it has cached from memory; a new name it must first ask the domain's own nameservers about. Google measured cache misses as the main cause of DNS latency (Google Public DNS), so this test times both, the way GRC's DNS Benchmark splits cached and uncached lookups.

The two numbers can rank resolvers differently. In the recorded run AdGuard DNS answered cached names in 63 ms but took 267 ms for new ones, while Cloudflare took 58 and 60 ms.

New names here are random labels under eight large zones run by different DNS providers (none hosted by Cloudflare or Google, so neither gets a home advantage). They don't exist, so nobody can have them cached.

  • NextDNStimed only50 ms54 ms
  • Cisco OpenDNStimed only55 ms46 ms
  • Cloudflare58 ms60 ms
  • AdGuard DNStimed only63 ms267 ms
  • Control D63 ms68 ms
  • Google Public DNS81 ms102 ms
  • CleanBrowsing197 ms209 ms
  • Yandex DNStimed only261 ms314 ms
  • IIJ Public DNS263 ms297 ms
  • DNS.SB296 ms295 ms
  • Quad9timed only319 ms345 ms
  • DNS4EU354 ms354 ms
Medians from the recorded run, sorted by the cached lookup. The ranking uses cached lookups; the new-name column shows who slows down on names nobody has asked for.

Is 1.1.1.1 faster than 8.8.8.8?

It depends on which site answers you. Both are anycast: Cloudflare's 1.1.1.1 and Google's 8.8.8.8 each answer from the nearest of their own data centres, and your network decides which one that is.

In the recorded run Cloudflare was 23 ms faster for cached names and 42 ms faster for new ones, both answering from India. Google also picked a different site between connections, which is why its lookups spread wider.

Run the test on your own Wi-Fi and on mobile data: the answer can flip.

Cloudflare1.1.1.1
Google8.8.8.8
58 msfaster
Cached lookup
81 ms
60 msfaster
New name
102 ms
133 msfaster
First connection
241 ms
98 msfaster
9 in 10 answered within
152 ms
Chennai
Answered from
Chennai
Each bar is relative within its row. Lower is better.

What is a good DNS response time?

Under about 75 ms is fast, up to 200 ms is fair, and slower usually means the answer comes from another continent. These are DNS Robot's own bands, drawn from distance, not an industry standard.

The floor is physics: about 1 ms per 100 km there and back. A resolver with a site in your city can answer cached names in 10–30 ms; one in the next country needs 30–80 ms; across an ocean, 150 ms or more.

A "DNS ping test" that pings 1.1.1.1 measures the path, not DNS: a resolver can answer a ping fast and still be slow to resolve a name. This test times real lookups.

DNS Robot's bands, from distance

505558636381197261263296319354
  • NextDNS: 50 ms
  • Cisco OpenDNS: 55 ms
  • Cloudflare: 58 ms
  • AdGuard DNS: 63 ms
  • Control D: 63 ms
  • Google Public DNS: 81 ms
  • CleanBrowsing: 197 ms
  • Yandex DNS: 261 ms
  • IIJ Public DNS: 263 ms
  • DNS.SB: 296 ms
  • Quad9: 319 ms
  • DNS4EU: 354 ms
Each mark is a resolver's cached median in the recorded run, on a log scale.

What is the fastest DNS server?

The one with a site closest to you that keeps popular names cached: there is no single fastest or best DNS server for everyone. Run this DNS benchmark on your own connection and it ranks the public resolvers for you.

Mind the route. From some networks DNS.SB's browser hostname answers from nearby (39 ms) while its address and its Private DNS name answer from Frankfurt (296 ms): most speed tests would crown it, but the address you'd actually set is slow. This test ranks the address you would set and shows both.

Speed isn't everything: what a resolver blocks, what it logs and whether it passes part of your address on (ECS) matter too. The table below lists them.

  1. 1NextDNStimed only50 ms
  2. 2Cisco OpenDNStimed only55 ms
  3. 3CloudflareChennai58 ms
  4. 4AdGuard DNStimed only63 ms
  5. 5Control DNavi Mumbai63 ms
  6. 6Google Public DNSChennai81 ms
  7. 7CleanBrowsingLondon197 ms
  8. 8Yandex DNStimed only261 ms
  9. 9IIJ Public DNSJapan263 ms
  10. 10DNS.SBFrankfurt296 ms↳ doh.dns.sbIndia · browser route, not the one you'd set39 ms
  11. 11Quad9timed only319 ms
  12. 12DNS4EUFrankfurt354 ms
Ranked by cached median. Timed-only rows rank too, but the verdict names a resolver whose answers were read and checked.

Which Private DNS hostname is fastest on Android?

Run the test on your phone: the fastest resolver with a Private DNS hostname is the one to type. Android's Private DNS (Android 9 and later) takes a hostname, typed into the Private DNS provider hostname field, not an IP address, and uses DNS over TLS; since 2022 Android 11+ uses DNS over HTTP/3 for Google and Cloudflare.

Type the hostname exactly: one.one.one.one for Cloudflare, dns.google for Google, dns.quad9.net for Quad9. A typo makes Android report "no internet access" on every network.

Some hostnames travel further than the address: DNS.SB's dot.sb went to Frankfurt in the recorded run. Read more in what is Private DNS.

ResolverPrivate DNS hostname
Cloudflareone.one.one.one
Google Public DNSdns.google
Quad9dns.quad9.net
Control Dp0.freedns.controld.com
AdGuard DNSdns.adguard-dns.com
CleanBrowsingsecurity-filter-dns.cleanbrowsing.org
DNS.SBdot.sbanswers from Frankfurt: 296 ms
DNS4EUunfiltered.joindns4.eu
IIJ Public DNSpublic.dns.iij.jp
Yandex DNScommon.dot.dns.yandex.net
NextDNSno public hostname
Cisco OpenDNSno public hostname
Settings › Network & internet › Private DNS on stock Android; Samsung: Settings › Connections › More connection settings › Private DNS.

How do I change my DNS server?

Set it on your router to cover every device on your Wi-Fi, or on one device to try it first. Each system keeps the setting in a different place; the values are the same everywhere.

On Windows 11 and a Mac you type the IPv4 addresses (Windows can add DNS over HTTPS); on an iPhone the setting is per Wi-Fi network; on Android, Private DNS takes the hostname. After running the test, the Switch panel shows the exact steps and values for your fastest resolver.

To undo, set DNS back to automatic. Nothing else on your device changes.

Windows 11

Settings › Network & internet › your network › DNS server assignment › Edit

Preferred DNS1.1.1.1
Alternate DNS1.0.0.1
DNS over HTTPSOn (automatic template)

Mac

System Settings › Network › Wi-Fi › Details › DNS

DNS Servers1.1.1.1
1.0.0.1
2606:4700:4700::1111

iPhone

Settings › Wi-Fi › ⓘ › Configure DNS › Manual

Configure DNSManual
1.1.1.1
1.0.0.1

Router

Admin page › Internet / WAN › DNS

Primary DNS1.1.1.1
Secondary DNS1.0.0.1
Filled in with Cloudflare's addresses. The Switch panel under the test fills in your fastest resolver's.

Best DNS for gaming: does a faster DNS make games faster?

Only the first visit to each site, by a few tens of milliseconds. DNS runs once per name; your device caches the answer, and the page, video or game data never touches DNS again.

For games, including BGMI, Free Fire and PUBG, DNS is looked up when you join; every move after that goes straight to the game's server. Your ping in the game depends on the route to that server, not on your DNS. A resolver that sends you to a far-away server can hurt, which is what ECS and a nearby site help with.

Where DNS does matter: a slow or failing resolver delays every new site you open, and a filtering resolver can block what you need.

A first visit to a site ≈ 1,078 ms

A 30-minute game session

DNS once, when you joinGame packets: never DNS
DNS from the recorded run (58 ms, Cloudflare's cached median); the other steps are typical, for scale.

Which DNS servers can a browser test, and which can't?

Any DNS over HTTPS server can be timed, but a web page can read only the answers of servers that allow it (a CORS header). Of the twelve here, seven allow it: Cloudflare, Google, Control D, CleanBrowsing, DNS.SB, DNS4EU and IIJ.

AdGuard DNS, NextDNS, Cisco OpenDNS and Yandex DNS send no CORS header. Quad9 sends it over HTTP/2 but not over HTTP/3, so browsers fail once they switch, measured in Chromium, Firefox and WebKit. These are timed only: the time is real, but the page can't check the answer or see where it came from.

Timed-only rows still rank, marked as such; the verdict always names a resolver whose answers were read.

This pagequeryDoH serverreply + Access-Control-Allow-Originanswer read and checked
This pagequeryDoH serverreply without the headeronly the time is known

Verified: answers read · 7

CloudflareGoogle Public DNSControl DCleanBrowsingDNS.SBDNS4EUIIJ Public DNS

Timed only · 5

  • Quad9drops the CORS header over HTTP/3
  • NextDNSsends no CORS header
  • AdGuard DNSsends no CORS header
  • Cisco OpenDNSsends no CORS header
  • Yandex DNSsends no CORS header
Measured by DNS Robot on 2026-10-22 in Chromium, Firefox and WebKit.

Who runs 8.8.8.8, 1.1.1.1 and 9.9.9.9?

Google runs 8.8.8.8 and 8.8.4.4 (Google Public DNS), Cloudflare runs 1.1.1.1 and 1.0.0.1, and the Quad9 Foundation, a Swiss non-profit, runs 9.9.9.9. Each is a free public resolver: it looks up names for anyone who sets it.

The best DNS servers differ in what they block, what they log and whether they pass part of your address on to the domain's servers (ECS, which helps CDNs pick a nearby server but tells them roughly where you are). The table sums up what each operator says on its own pages.

ServiceRun byAddressesPrivate DNSBlocksLogsECSDNSSEC
CloudflareCloudflare, Inc.1.1.1.11.0.0.1one.one.one.oneno filteringDeleted within 25 hours; your address never written to disknoyes
Google Public DNSGoogle LLC8.8.8.88.8.4.4dns.googleno filteringYour address kept 24–48 hours; a sample without it, longeryes: part of your address (/24)yes
Quad9Quad9 Foundation9.9.9.9149.112.112.112dns.quad9.netblocks malwareYour address not recordednoyes
Control DControlD Inc.76.76.2.076.76.10.0p0.freedns.controld.comno filteringNo query logs on the free resolversnot publishednot published
NextDNSNextDNS Inc.not published—your own filtersNothing, unless you turn logs onits own ECS, without your addressyes
AdGuard DNSAdguard Software Ltd94.140.14.1494.140.15.15dns.adguard-dns.comblocks ads & trackersNo personal data; anonymous domain countsa stand-in subnet, not yoursnot published
Cisco OpenDNSCisco208.67.222.222208.67.220.220—blocks phishingNot publishednot publishednot published
CleanBrowsingCleanBrowsing, Inc.185.228.168.9185.228.169.9security-filter-dns.cleanbrowsing.orgblocks phishing, malware, spamNo personal data on the free filtersnot publishednot published
DNS.SBxTom GmbH185.222.222.22245.11.45.11dot.sbno filteringNo query logsnoyes
DNS4EUWhalebone s.r.o. (EU-backed)86.54.11.10086.54.11.200unfiltered.joindns4.eucourt-ordered blocks only“Queries are anonymised”; no retention period publishednot publishednot published
IIJ Public DNSInternet Initiative Japan Inc.not publishedpublic.dns.iij.jpblocks child-abuse sites onlySource address cut to a /22; deleted within 24 hoursnot publishednot published
Yandex DNSYANDEX LLC77.88.8.877.88.8.1common.dot.dns.yandex.netno filteringMay record the sites you visit and share them with Yandex companiesnot publishednot published
From each operator's own pages, checked 2026-10-22. Yandex's terms let it record the sites you visit (YANDEX LLC, Russia); IIJ Public DNS is a trial until 31 March 2027.

DNS speed test: questions

What is the fastest DNS server?

There is no single fastest DNS server: it depends on which of each resolver's sites your network reaches. Cloudflare 1.1.1.1, Google 8.8.8.8 and Quad9 9.9.9.9 all answer from the nearest of their data centres, and the nearest differs by city and provider. Run this DNS speed test on your own connection; it ranks the fastest DNS server for you and shows where each answer came from.

Is 1.1.1.1 faster than 8.8.8.8?

Often, but not everywhere. Both are anycast, so each answers from its own nearest site, and the winner depends on your network. In our recorded run from India, Cloudflare's 1.1.1.1 answered cached names faster than Google's 8.8.8.8 and both answered from India. Within 5 ms of each other, this test calls it a tie rather than inventing a winner.

Who is 9.9.9.9?

9.9.9.9 is Quad9, a free public DNS resolver run by the Quad9 Foundation, a Swiss non-profit. It blocks domains known for malware and phishing, does not record users' IP addresses, validates DNSSEC and doesn't pass part of your address on (ECS), except on its 9.9.9.11 variant. A web page can time it but not read its answers over HTTP/3.

What do 8.8.8.8 and 8.8.4.4 do?

They are Google Public DNS's two IPv4 addresses: free resolvers that look up domain names for any device that sets them, with 8.8.4.4 as the backup. Google keeps your IP address in temporary logs for 24 to 48 hours, validates DNSSEC and passes the first part of your address (a /24) to domain servers so CDNs can pick a nearby server.

What is a good DNS ping in ms?

For cached lookups, under about 75 ms is fast, up to 200 ms is fair, and more usually means the answer crosses a continent. These are our own bands from distance: light in fibre needs about 1 ms per 100 km there and back. A DNS ping test that only pings the server's address measures the path, not DNS; this test times real lookups.

Can this DNS test see my current DNS?

Yes. Your browser looks up random names that only our own test nameserver answers, and our nameserver sees which resolver asked: your provider's, a public one, or a VPN's. It is timed on brand-new names only, because your browser caches its own answers. The resolver's address, and the part of your IP address it passes on if it does (ECS), is kept for 10 minutes to show you the result, then deleted.

Why do my results change every time?

Resolvers pick a site per connection, your line has busy moments, and caches expire. Medians keep one slow lookup from deciding the ranking, and results within 5 ms count as a tie. Results also differ between Wi-Fi and mobile data, which reach the resolvers by different routes: run a DNS speed test on each, and compare them under Past runs.

Is it safe to change my DNS, and what do these services log?

Yes: changing DNS only changes who looks up names for you, and you can undo it any time. What they log differs: Cloudflare deletes logs within 25 hours, Google keeps your address 24–48 hours, Quad9 records no addresses, and Yandex may record the sites you visit. The table above quotes each operator's own policy.

What is the best Private DNS for Android?

The fastest from your phone that blocks what you want. Run this test on the phone itself, on Wi-Fi and mobile data, then type that resolver's Private DNS hostname in Settings › Network & internet › Private DNS: one.one.one.one for Cloudflare, dns.google for Google, dns.quad9.net for Quad9, dns.adguard-dns.com to block ads.

What is the best DNS server for gaming (BGMI, Free Fire, PUBG)?

Any fast, reliable one: DNS runs once when you join a match, and your in-game ping depends on the route to the game server, not on DNS. Pick the fastest resolver from this test, preferably one that passes your region on (ECS) or has a site near you, so the game sends you to a nearby server.

How is this different from GRC DNS Benchmark or namebench?

Like GRC's DNS Benchmark, this DNS benchmark tool times cached and uncached (new-name) lookups, but it runs in your browser with nothing to install, over encrypted DNS (DoH), and shows where each answer came from. namebench is no longer maintained. A browser can't send plain DNS on port 53, so resolvers without DNS over HTTPS can't be tested here.

Why is Quad9 (or AdGuard) marked "timed only"?

Because a web page can't read their answers. AdGuard DNS, NextDNS, Cisco OpenDNS and Yandex DNS send no CORS header, and Quad9 drops it over HTTP/3. The browser still sees when the reply arrives, so the time is real, but it can't check the answer or read where it came from. They rank with a timed-only mark and are never crowned without a note.

Missing something?Suggest a feature or a new tool

More DNS and network tools