← Blog Β· May 23, 2026 Β· dns, performance

Public DNS Resolvers: 1.1.1.1 vs 8.8.8.8 vs 9.9.9.9

If you just want an answer β€” use 1.1.1.1 (Cloudflare) for raw speed,9.9.9.9 (Quad9) if you want malware-domain filtering, and 8.8.8.8 (Google) when those two are blocked on a hotel network. All three are free, anycast, DNSSEC-validating, and support DoH/DoT.

The numbers

DNSPerf has been benchmarking public resolvers since 2017. Long-running 2025 medians from their global probes:

ResolverPrimary IPv4SecondaryMedian global latencyFiltering
Cloudflare1.1.1.11.0.0.1~11 msNone (default) β€” 1.1.1.2 blocks malware, 1.1.1.3 blocks malware + adult
Google8.8.8.88.8.4.4~18 msNone
Quad99.9.9.9149.112.112.112~22 msBlocks domains on threat-intel feeds (~3M malicious hosts)
OpenDNS (Cisco)208.67.222.222208.67.220.220~24 msOptional category filtering via account
AdGuard DNS94.140.14.1494.140.15.15~27 msBlocks ads + trackers + (optional) adult content

Latency varies wildly by location β€” Cloudflare wins almost everywhere in North America and Europe, but in some parts of Asia Quad9 or Google edge ahead because of where their POPs land.

Privacy policies β€” actually read them once

DoH and DoT β€” encrypt your queries

Plain DNS (port 53) is unencrypted. Your ISP, hotel WiFi, and anyone on the path can read every domain you visit. All four resolvers above support encrypted DNS:

Firefox and Chrome both support DoH natively. iOS 14+ and macOS 11+ support both DoH and DoT via configuration profiles. Android 9+ does DoT as "Private DNS."

The decision tree

  1. Want the fastest resolver and don't care about filtering β€” 1.1.1.1.
  2. Want automatic malware-domain blocking with no setup β€” 9.9.9.9.
  3. Want family-safe filtering (block adult content) β€” 1.1.1.3.
  4. Want to block ads at the DNS layer β€” AdGuard DNS or run your own Pi-hole.
  5. Want maximum privacy with zero IP logging β€” Quad9.
  6. On a network that blocks the others β€” 8.8.8.8 is allowed almost everywhere.

Test before you commit

Latency varies by your physical location and ISP route. Measure from your own network with dig @1.1.1.1 example.com or use a benchmarking tool like DNS Benchmark or namebench. A 30 ms difference in DNS lookup is invisible for most browsing β€” only worth caring about if you make thousands of lookups per minute (build servers, CI runners, web crawlers).

One more thing β€” your ISP's resolver might already be fine

ISPs in major markets now run anycast DNS with sub-10ms latency to subscribers. The reason to switch is rarely speed β€” it's privacy, filtering, or escaping ISP-level DNS hijacking (where typos redirect to ad pages). If your ISP doesn't do those, you're probably fine staying put.

Related tools

← All blog posts