DNS

Best DNS Servers: ISP vs Google vs Cloudflare vs Quad9, Tested

Best DNS servers compared from provider docs: ISP, Google 8.8.8.8, Cloudflare 1.1.1.1, Quad9 9.9.9.9. Privacy, filtering, DNSSEC and how to test speed yourself.

In this guide

There is no single winner among the best DNS servers. The fastest one is whichever answers quickest from your own connection, which you can measure yourself. Beyond speed, choose by what you need the resolver to do, such as malware blocking (Quad9, Cloudflare 1.1.1.2), ad blocking (AdGuard), parental filtering (OpenDNS FamilyShield, Cloudflare 1.1.1.3), or the strictest logging policy.

Test it now

Cloudflare edge
IP websites see216.73.216.115
LocationColumbus, United States
Internet providerAnthropic, PBC

Read at the Cloudflare edge from this request. The homepage adds your provider, network type and the VPN, DNS and WebRTC checks.

Show details

What a DNS server does for you, and what changing DNS does (and does not do) to speed

A DNS server, properly a recursive resolver, turns the names you type into the IP addresses your device connects to. Your device asks it once per name, then caches the answer for as long as the domain owner allows: RFC 1034 defines the TTL as the field that "describes how long a RR can be cached before it should be discarded." After that first lookup, the page, video or game session flows between your device and the destination's address, and the resolver is out of the picture.

That is the whole effect of changing DNS. A faster resolver shortens the pause before a new site starts loading, and only for names not already in your cache. It does not raise your download speed, lower your ping to a game server, or change what a website sees about you. It can change what you can reach, since filtering services refuse to answer for domains on their lists, and a resolver far from you can steer you to a far-away content server, which the CDN section explains. Google's FAQ adds the point most "fastest DNS" lists miss: "In addition to the ping time, you also need to consider the average time to resolve a name," because a lower ping with a colder cache can be slower overall. The test below measures both.

What DNS am I using? See your current resolver now

Open the DNS server check. It loads a unique hostname under the site's own test zone, which exists only on its nameserver, so "whichever resolver asks for it is the one your device really uses." The result shows the resolver's IP address, its operator and country (Cloudflare, Google, Quad9 and OpenDNS are recognized by ASN), whether a client subnet was forwarded, and fields for DNSSEC and encrypted DNS. If the resolver address is your own public IP, you are running a local resolver such as Pi-hole or Unbound.

Most home devices use whatever the router hands out over DHCP, normally the ISP's resolver; Microsoft's Windows documentation describes the default DNS server address as "set automatically by your router or other access point." If you see your ISP's name here, you have never changed DNS. For a longer check that catches systems using more than one resolver, run the DNS leak test, which reports every resolver that answered.

The best DNS servers compared

Everything in this table comes from each provider's own documentation, dated where the page gives a date. "Not stated" means the pages reviewed did not say, not that the feature is absent.

ResolverIPv4 addressesEncrypted DNSDNSSEC validationFilteringEDNS Client SubnetLogging, per the provider's policy
Your ISPAssigned by your router via DHCPVariesVariesVariesUsually unnecessary; the resolver is inside your ISP's networkRead your ISP's privacy policy
Google Public DNS8.8.8.8, 8.8.4.4 (IPv6 2001:4860:4860::8888, ::8844)DoT (dns.google, port 853) and DoHYes, "a validating, security-aware resolver"None, "except for certain domains in rare cases"Yes, sent to nameservers that support itTemporary logs with the client IP deleted within 24-48 hours; permanent logs replace the IP with a city or region (policy 2024-09-03)
Cloudflare 1.1.1.11.1.1.1, 1.0.0.1 (IPv6 2606:4700:4700::1111, ::1001)DoT (one.one.one.one, port 853, RFC 7858) and DoHYes, "a DNSSEC-validating resolver"1.1.1.2 / 1.0.0.2 block malware; 1.1.1.3 / 1.0.0.3 block malware and adult contentNo: "does not include client IP information in its queries"Logs deleted within 25 hours; source IP not kept in non-volatile storage, truncated before use; no sale, no ad targeting (policy March 27, 2024)
Quad99.9.9.9, 149.112.112.112 (IPv6 2620:fe::fe, 2620:fe::9)DoT (dns.quad9.net) and DoH (https://dns.quad9.net/dns-query)YesMalware blocking from about twenty threat-intelligence sources; "does not block content"; 9.9.9.10 is unfilteredOnly on the 9.9.9.11 service"Quad9 does not collect or record user IP addresses" (policy v1.1, June 24, 2026)
OpenDNS (Cisco)208.67.222.222, 208.67.220.220; FamilyShield uses separate addressesNot stated on the pages reviewedNot stated on the pages reviewedHome: "customizable filtering and basic protection"; FamilyShield: "pre-configured to block adult content"Not statedNot stated on the pages reviewed
AdGuard DNS94.140.14.14, 94.140.15.15 (default); 94.140.14.140, .141 (non-filtering); 94.140.14.15, 94.140.15.16 (family)DoT (tls://dns.adguard-dns.com) and DoH (https://dns.adguard-dns.com/dns-query)Not stated on the pages reviewedDefault blocks ads and trackers; family mode adds adult content and safe searchNot stated"We do not process any of your Personal Data when you connect to and use public AdGuard DNS"; anonymous database of domains for 24 hours (policy August 6, 2024)
NextDNS, Control DPer-account or per-profile addressesDoT and DoHNot statedConfigurable blocklistsNot statedNextDNS: "If not specifically requested by the user, no data is logged." Control D: "We don't log or store your DNS queries."

One note on reading it: DNSSEC validation protects you from forged answers (RFC 4033 describes "data origin authentication and data integrity") but "does not provide confidentiality"; encryption is DoT and DoH's job.

Which DNS is fastest? Test it from your own connection

Published rankings cannot answer this for you. DNSPerf, the usual source for them, tests "every minute from 200+ locations globally" over IPv4 and publishes hourly aggregates you can filter by region; that shows how a resolver performs from DNSPerf's probes, not from your line, and your ISP may route you to a different data center. Fifteen minutes with the commands below settles it.

  1. Record your baseline with the ping test. It runs three measurements without input: your browser to the site's Frankfurt server, your browser to the nearest Cloudflare edge, and the Frankfurt server to your public IP. The browser-to-edge figure is the floor your connection can reach, so a candidate within a few milliseconds of it is as fast as your line allows. The page cannot ping arbitrary hosts from your device, because browsers cannot send ICMP, which is why the next steps run on your computer.
  2. Ping each candidate from your computer, ten times each: on Windows, ping -n 10 8.8.8.8; on macOS or Linux, ping -c 10 8.8.8.8. Repeat for 1.1.1.1, 9.9.9.9 and your ISP's resolver address from step one of the previous section. Note the average and whether any packets were lost.
  3. Time actual lookups. On macOS or Linux, dig @1.1.1.1 example.com prints query statistics after each lookup by default, including the query time; the BIND manual describes the argument as "the name or IP address of the name server to query." In Windows PowerShell, Measure-Command { Resolve-DnsName example.com -Server 1.1.1.1 } runs the lookup against the server you name and returns a time span whose TotalMilliseconds field is the lookup time.
  4. Run each lookup twice, then repeat with five or ten names you actually use. The first answer is a hit or a miss depending on whether someone near you asked recently; the second is a cache hit and shows the pure round trip. A resolver with many users behind your nearest server has a warmer cache and wins first queries more often, the effect Google's FAQ describes.
  5. Use the DNS lookup tool to compare answers rather than times. It asks Cloudflare 1.1.1.1 and Google 8.8.8.8 over DNS over HTTPS at once, "skips your resolver and asks two public ones directly," and highlights any difference record by record. A name that resolves on one and not the other is filtering or propagation lag, not speed.

Keep whichever candidate gives the lowest lookup times with no packet loss. If two are within a few milliseconds, the difference is below what you will notice, and the next sections should decide.

Privacy and security: logging policies, encrypted DNS, DNSSEC validation, malware filtering

Logging. The table quotes each policy; the differences are in retention and in what is kept. Google keeps temporary logs "subject to our deletion processes within 24-48 hours" and strips the IP from permanent logs. Cloudflare "will delete the Public Resolver Logs within 25 hours," does not keep the source IP "in non-volatile storage," and says it has retained "one of the top four accounting firms to audit our practices." Quad9 says the address "is held only in volatile memory" and that it "does not share, sell, or rent any information that could identify an individual user," under Swiss data-protection law. AdGuard keeps "an anonymous database of domains requested in the last 24 hours" with "no information whatsoever that could link any of these domain names to the original user." Your ISP's policy is whatever its privacy statement says, and it sees your traffic's destinations whether or not it runs your DNS.

Encryption. Plain DNS is readable by anyone on the path. RFC 7858 defines DNS over TLS on port 853 and RFC 8484 defines DNS over HTTPS, "a protocol for sending DNS queries and getting DNS responses over HTTPS." Google, Cloudflare, Quad9 and AdGuard all publish DoT and DoH endpoints (see the table). Encryption hides your queries from the network you are on, not from the resolver, which is why the logging policy matters more once encryption is on. The DNS server check reports encrypted DNS when it can detect it, and notes that whether the last hop from your device was encrypted "is determined by your settings." A network that blocks DoH or DoT is what triggers the iPhone warning explained in “This network is blocking encrypted DNS traffic”.

DNSSEC. A validating resolver checks the signatures on signed domains before answering. Google, Cloudflare and Quad9 all document validation, including Quad9's unfiltered 9.9.9.10.

Filtering. Quad9 "refuses to answer with the IP address" for domains on its threat feeds and says plainly that it "does not block content" or advertisements. Cloudflare's 1.1.1.2 and 1.1.1.3 add malware and adult-content blocking. AdGuard's default servers "block ads and trackers," and its family servers add adult content and safe search. OpenDNS FamilyShield is "pre-configured to block adult content" with no account. Google does none of this. A blocked page looks like a broken site, so anyone on a filtered resolver should know it is there.

Best DNS for PS5, Xbox and gaming: what a resolver can and cannot fix

A console resolves a handful of names when it signs in, finds a matchmaking service or starts a download, then talks to those servers by address. In-game latency is the round trip between your console and the game server, packet loss is a property of your line and Wi-Fi, and NAT type is decided by your router; a DNS change touches none of them. The what is ping guide covers what actually moves those numbers.

What a resolver can do for a console is answer reliably and quickly, so store pages, friend lists and download starts do not stall on a slow or failing ISP resolver, and avoid filtering that breaks a game's services. The honest "best DNS for PS5" is the one your own test picked, entered in the console's manual DNS settings below. If voice chat or a party system breaks after a DNS change, suspect filtering first and switch to an unfiltered address such as 9.9.9.10 or 1.1.1.1.

The CDN caveat: EDNS Client Subnet and why a far-away resolver can slow downloads

Large sites answer DNS queries differently depending on where the query comes from, so that you download from a nearby server. With a public resolver, the authoritative server sees the resolver's address, not yours. Google's FAQ describes the result: "the resolver may not be in close proximity to the users," and "In such cases, the browsing experience could be slowed down somewhat."

EDNS Client Subnet is the fix and the trade-off. RFC 7871 defines an option "to carry information about the network that originated a DNS query" to the authoritative server, recommends truncating it to 24 bits of an IPv4 address or 56 bits of IPv6, and states the cost: "the network address of the client that initiated the resolution becomes visible to all servers involved in the resolution process." Google sends ECS to nameservers it detects as supporting it. Cloudflare's FAQ answers "No" to sending ECS, describing 1.1.1.1 as "a privacy-focused resolver." Quad9 offers ECS only on 9.9.9.11. The DNS server check shows whether your resolver forwards a client subnet, and the DNS leak test reports the subnet it saw. If downloads from big services slow down after switching to a non-ECS resolver, that is the mechanism, and the remedy is an ECS-enabled resolver or your ISP's.

How to change DNS on Windows, macOS, iPhone, Android and your router, then verify

Write down the current settings first, as Google's setup guide advises, so you can switch back. Each path below comes from the vendor's documentation named in the sources.

  1. Windows 11. Open Settings, go to Network and Internet, and select the adapter you use. Scroll to DNS server assignment and select Edit, change Automatic (DHCP) to Manual, turn on IPv4, enter the preferred and alternate addresses, optionally do the same for IPv6, then Save (Cloudflare's Windows guide, May 1, 2026). Microsoft's documentation describes a DNS over HTTPS choice in Windows 11's DNS settings, Off, On (automatic template) or On (manual template), and notes the setting "is not available in Windows 10."
  2. Windows 10. Settings, Network and Internet, Change Adapter Options, right-click the active connection and choose Properties, select Internet Protocol Version 4, Properties, then Use the following DNS server addresses and OK.
  3. macOS. Apple's guide (macOS User Guide, versions through macOS 27) gives one path: "choose Apple menu > System Settings, click Network in the sidebar, click a network service, click Details, then click DNS." Add the addresses there.
  4. iPhone and iPad. Apple's iOS 27 guide: open Settings, tap Wi-Fi, tap the info button next to the network, then "Configure DNS, HTTP Proxy, and other network settings: Tap a setting, then enter the details." Cloudflare's iOS guide spells out the taps: Configure DNS, change Automatic to Manual, Add Server, enter the address, Save. The setting applies to that Wi-Fi network only.
  5. Android. Android's help page: open Settings, tap Network & internet, then Private DNS, choose Private DNS provider hostname, and enter a DoT hostname such as dns.google, one.one.one.one or dns.quad9.net, then Save; some steps "work only on Android 12 and up." This encrypts the queries as well as changing the resolver. The Private DNS guide covers the hostnames and the "cannot be accessed" error.
  6. Router. Changing the DNS the router hands out over DHCP moves every device at once. The menu differs by brand; TP-Link's documentation, for example, uses Advanced > Network > DHCP Server, where you enter the primary and secondary DNS and Save.
  7. PS5. Sony's guide: Settings > Network > Settings > Set Up Internet Connection, choose your network, then Advanced Settings, where DNS is among the items you can adjust. Xbox One: Settings > Network > Network Settings > Advanced Settings > DNS Settings, then Manual (Cloudflare's console guide).

Then verify. Flush the cache first, since old answers stay until their TTL expires; the flush DNS guide has the command for each system. Reload the DNS server check and confirm the operator is the one you chose, then run the DNS leak test to confirm no other resolver is still answering. If the ISP's resolver still shows, the device is still taking DNS from DHCP: check the adapter you actually use, or set it on the router instead.

Decision guide: who should pick what

  • Your test showed the ISP resolver is fast and reliable. Keep it. It sits inside your ISP's network and usually needs no ECS to place you correctly.
  • You want accurate CDN placement and no filtering. Google: DNSSEC validation, DoT and DoH, ECS on; logs with your IP deleted within 24-48 hours.
  • You want the shortest log retention and no ECS. Cloudflare 1.1.1.1: logs deleted within 25 hours, source IP truncated and not kept; accept that some downloads may route less precisely.
  • You want malware blocking without content filtering. Quad9 9.9.9.9, run by a Swiss foundation that says it does not record user IP addresses; use 9.9.9.11 if you want ECS back.
  • You want to block ads network-wide. AdGuard's default servers, or a configurable service such as NextDNS or Control D.
  • You are setting up a child's device or a family router. OpenDNS FamilyShield, Cloudflare 1.1.1.3 or AdGuard's family servers, whichever your speed test favored.
  • You game on a console. Whichever unfiltered resolver won your test; expect no change in ping.

Whatever you pick, the measurement is the part that transfers. Resolver networks and ISP routing change, and a winner from a list written somewhere else is a guess until you have run the test from your own connection.

Sources

  1. Google Public DNS, Get Started (addresses and setup; last updated 2024-09-03)
  2. Google Public DNS, Privacy policy (last updated 2024-09-03)
  3. Google Public DNS, FAQ (last updated 2026-10-13)
  4. Google Public DNS, DNS-over-TLS (last updated 2024-09-03)
  5. Google Public DNS, EDNS Client Subnet (ECS) Guidelines (last updated 2024-09-03)
  6. Cloudflare Docs, 1.1.1.1 IP addresses (last updated April 30, 2026)
  7. Cloudflare Docs, 1.1.1.1 Public DNS Resolver privacy commitments (page dated May 6, 2026; policy text March 27, 2024)
  8. Cloudflare Docs, 1.1.1.1 FAQ (last updated April 30, 2026)
  9. Cloudflare Docs, 1.1.1.1 Setup, including 1.1.1.1 for Families addresses (last updated May 6, 2026)
  10. Cloudflare Docs, DNS over TLS (last updated May 6, 2026)
  11. Cloudflare Docs, Set up 1.1.1.1 on Windows (last updated May 1, 2026)
  12. Cloudflare Docs, Set up 1.1.1.1 on iOS (last updated May 1, 2026)
  13. Cloudflare Docs, Set up 1.1.1.1 on gaming consoles (last updated May 1, 2026)
  14. Quad9, Service addresses and features
  15. Quad9, Privacy policy, version 1.1 (June 24, 2026)
  16. Quad9, Threat blocking
  17. Quad9, About
  18. OpenDNS (Cisco), Home Internet Security (OpenDNS Home and FamilyShield)
  19. OpenDNS (Cisco), Setup Guide (nameserver and FamilyShield addresses)
  20. AdGuard DNS, Public DNS servers (addresses and filtering modes)
  21. AdGuard DNS, Privacy policy (August 6, 2024)
  22. NextDNS, Privacy policy
  23. NextDNS, home page (DNS-over-HTTPS and DNS-over-TLS support)
  24. Control D, Free DNS
  25. RFC 7871, Client Subnet in DNS Queries (IETF, May 2016, Informational)
  26. RFC 8484, DNS Queries over HTTPS (DoH) (IETF, October 2018)
  27. RFC 7858, Specification for DNS over Transport Layer Security (TLS) (IETF, May 2016)
  28. RFC 4033, DNS Security Introduction and Requirements (IETF, March 2005)
  29. RFC 1034, Domain Names - Concepts and Facilities (IETF, November 1987)
  30. DNSPerf, DNS performance analytics (methodology notes on the home page)
  31. Microsoft Support, Essential network settings and tasks in Windows (Change TCP/IP settings; updated 2026)
  32. Microsoft Learn, Resolve-DnsName (DnsClient module)
  33. Microsoft Learn, Measure-Command
  34. BIND 9 manual pages, dig
  35. Apple Support, Change DNS settings on Mac (macOS User Guide)
  36. Apple Support, Manage Wi-Fi settings on iPhone (iPhone User Guide, iOS 27)
  37. Android Help, Manage advanced network settings on your Android phone (Private DNS)
  38. PlayStation Support, How to set up an internet connection on PlayStation consoles (March 2026)
  39. TP-Link Support FAQ 1556 (router DHCP DNS setting path; updated April 20, 2026)

Questions

Is 208.67.222.222 OpenDNS?

Yes. OpenDNS, now part of Cisco, lists 208.67.222.222 and 208.67.220.220 as its nameservers. They serve OpenDNS Home, the free service with customizable filtering; OpenDNS FamilyShield, pre-configured to block adult content, uses a separate pair of addresses published in the OpenDNS setup guide.

What does DNS 8.8.8.8 and 8.8.4.4 do?

They are the two IPv4 addresses of Google Public DNS, a free recursive resolver. Point a device at them and it sends its name lookups to Google instead of your ISP. Google's documentation says the service validates DNSSEC, supports DNS over TLS and HTTPS, and does no filtering except for certain domains in rare cases.

Who is 9.9.9.9 DNS?

9.9.9.9 is Quad9, a free anycast resolver run by the Swiss foundation Quad9, hosted care of SWITCH in Zurich, with Global Cyber Alliance, IBM and PCH as founding organizations. Its default service blocks domains from threat-intelligence feeds and validates DNSSEC; 9.9.9.10 is the unfiltered variant.

Is 1.1.1.1 or 8.8.8.8 faster?

It depends on where you are and which has a nearer server and a warmer cache for the names you look up. Google's own FAQ says ping time alone is not the measure; resolution time across many names is. Test both from your connection using the method above and keep whichever wins.