By Clinton Patrick · Published 2026-05-27 · Updated 2026-05-27
Live 30-day median (p50) latency for the 14 public DNS resolvers that WhereIsDNS queries on every lookup. Measurements come from a Cloudflare Workers cron that samples every resolver every four hours from the same edge location, so the numbers compare apples to apples.
Live leaderboard
Sorted by 30-day p50 latency, lowest first. Click a column header to re-sort. Numbers update as the cron runs (every four hours, UTC).
Resolver
Region
p50 (ms)
Min
Max
Days
30-day trend
Cloudflare
Global anycast (~300+ POPs)
—
—
—
—
Google
Global anycast
—
—
—
—
Quad9
Global anycast
—
—
—
—
OpenDNS
Global anycast
—
—
—
—
AdGuard
Global anycast
—
—
—
—
NextDNS
Global anycast
—
—
—
—
Yandex
Russia + CIS
—
—
—
—
AliDNS
China-mainland focus
—
—
—
—
DNSPod
China-mainland focus
—
—
—
—
CleanBrowsing
Global anycast (US-centric)
—
—
—
—
Mullvad
EU + North America anycast
—
—
—
—
ControlD
Global anycast
—
—
—
—
Hurricane Electric
Global
—
—
—
—
DNS4EU
EU-only
—
—
—
—
Loading live data from /api/history…
How we measure
WhereIsDNS's Cloudflare Worker has a cron trigger that fires every four hours. On each firing, the Worker resolves a rotating test domain (example.com, cloudflare.com, google.com, wikipedia.org) via DNS-over-HTTPS against all 14 resolvers in parallel, records the latency-in-milliseconds for each successful response, and writes the values into Cloudflare KV.
At UTC midnight each day, the intraday samples roll up into the 30-day window as a median per resolver. Failures (timeouts, NXDOMAIN, SERVFAIL) are not recorded as latency points: we want the median of successful samples, not to penalize a resolver for one bad reading.
All sampling happens from the same Cloudflare edge that runs the live lookup tool. This is honest about what the numbers represent: latency from a Cloudflare edge POP, not from your home network. A resolver that's slow for us may be fast for you (or vice versa) depending on where you are and how your network is routed. The leaderboard is best read as a relative comparison between resolvers, not an absolute claim about user experience.
The full sampling code is in worker/index.ts (scheduled handler) and worker/history.ts (storage layer). Sample interval, test domains, and the rolling window size are all explicit constants in those files.
What the latency numbers mean
The headline number is 30-day median (p50) latency in milliseconds. Median, not mean: one slow sample can pull a mean wildly off, while p50 reflects the typical response time.
For end-to-end web performance, single-digit DNS latency (anything below ~10ms) feels essentially instant. The 10–50ms band is fast and well-engineered. 50–150ms is "noticeable on a cold lookup" but invisible once cached. Anything above 200ms suggests the query is crossing a region — either the resolver doesn't have a POP near our test edge, or routing is suboptimal.
The Chinese and Russian resolvers (AliDNS, DNSPod, Yandex) will always look slow from a Western edge; that's geography and routing, not a quality signal. Their inclusion in the leaderboard is to give the "what does a Chinese / Russian user see" data point during global propagation checks, not to claim they're slow at serving local users.
The "Days" column shows how many days of samples a resolver has contributed. Newer resolvers (or ones added recently to WhereIsDNS) will show fewer days until the 30-day window fills.
Per-resolver profiles
Operator, primary IP, region focus, and what makes each resolver distinct. The "Good default for" notes are practical recommendations based on what each one actually does well, not feature-list parity.
Cloudflare
1.1.1.1 · Cloudflare, Inc.
Global anycast (~300+ POPs)
Fastest in most regions; minimal logging by policy.
Cloudflare's 1.1.1.1 is the fastest public resolver in most regions thanks to an aggressive anycast footprint and well-peered transit. Cloudflare publishes a privacy policy committing to not write query logs to disk and to discard in-memory traces within 24 hours; KPMG audits this annually. The trade-off for performance and privacy: Cloudflare does not send EDNS Client Subnet by default, which can lead to less-optimal GeoDNS routing for sites that depend on it. Good default for: privacy-conscious users, low-latency lookups, and developers who want reliable global performance.
30-day p50—samples—
Google
8.8.8.8 · Google LLC
Global anycast
Best EDNS Client Subnet support; widely deployed.
Google Public DNS at 8.8.8.8 was the first mass-market anycast resolver and remains one of the most-used. It supports EDNS Client Subnet by default, which means GeoDNS-routed services typically get better answers through Google than through Cloudflare. Logging is more aggressive than Cloudflare's (temporary full logs, anonymized after 48 hours), which is the visible trade-off. Good default for: developers debugging GeoDNS, users on networks where Cloudflare is rate-limited or blocked, and anyone wanting a globally-available second resolver alongside 1.1.1.1.
30-day p50—samples—
Quad9
9.9.9.9 · Quad9 Foundation (Switzerland)
Global anycast, EU-headquartered
Blocks known malicious domains; non-profit, Swiss-based.
Quad9 is run by a non-profit foundation based in Zurich. Its differentiator is built-in threat blocking: 9.9.9.9 consults real-time threat-intelligence feeds and returns NXDOMAIN for known malware/phishing domains. There's also 9.9.9.10 (no filtering) and 9.9.9.11 (filtering + ECS). Latency is generally higher than Cloudflare or Google because of the smaller POP footprint, particularly in Asia and South America. Good default for: small business and family use where automatic malware blocking is more valuable than the last 20ms of latency.
30-day p50—samples—
OpenDNS
208.67.222.222 · Cisco Systems
Global anycast
Optional content filtering; long-running US operator.
OpenDNS has been around since 2005 and is now part of Cisco's Umbrella security platform. The free tier at 208.67.222.222 offers basic phishing protection and optional category-based content filtering (configurable on an account dashboard). It's a popular choice in schools and small offices for that filtering. Performance is solid in North America and Western Europe, weaker in Asia. Good default for: parents who want a simple "block adult content" setup without installing client software, or organizations that already use Cisco Umbrella.
30-day p50—samples—
AdGuard
94.140.14.14 · AdGuard Software Ltd. (Cyprus)
Global anycast, EU-centric
Blocks ads + trackers at the DNS layer.
AdGuard DNS at 94.140.14.14 filters ad and tracker domains by default, making it a network-wide adblocker without any per-device configuration. There's also a "Family Protection" endpoint (94.140.14.15) that additionally blocks adult and malware domains. Latency is best in Europe and the Middle East; usable elsewhere. The trade-off: any DNS-layer blocklist will occasionally over-block legitimate domains (CDN trackers that double as functional assets, for instance). Good default for: users who don't want browser-level adblockers, or routers that should filter for every device.
30-day p50—samples—
NextDNS
Per-account anycast · NextDNS Inc.
Global anycast
Per-user customizable blocklists; free tier with quotas.
NextDNS gives each user their own configuration (blocklists, allowlists, logging preferences, parental controls). The free tier allows 300,000 queries per month, which is generous for a single household. Setup involves creating a profile and pointing devices at a per-account DoH/DoT endpoint or one of the rotating IPs. Performance is competitive with the major anycast operators. Good default for: power users who want granular control over blocklists, want detailed query logs they actually own, or are managing DNS for a small group.
30-day p50—samples—
Yandex
77.88.8.8 · Yandex LLC (Russia)
Russia + CIS, some EU presence
Best latency for Russian / CIS users; Cyrillic-language defaults.
Yandex DNS at 77.88.8.8 is the dominant public resolver for users in Russia and the CIS region. It offers three modes: basic, "safe" (blocks malware), and "family" (additionally blocks adult content). Latency from Western Europe and North America is noticeably higher than the other globally-distributed operators. WhereIsDNS queries it primarily for cross-regional consensus: if a record looks healthy at every Western resolver but Yandex returns something different, that's a meaningful signal.
30-day p50—samples—
AliDNS
223.5.5.5 · Alibaba Cloud (China)
China-mainland focus, some APAC
Best performance from mainland China.
AliDNS at 223.5.5.5 is run by Alibaba Cloud. Like Yandex, its latency from outside its home region is high — typically several hundred milliseconds from Europe or the Americas. From within mainland China it's one of the fastest and most reliable resolvers available. WhereIsDNS queries AliDNS to surface how a given record actually looks to Chinese users, which can differ meaningfully from the Western view when GeoDNS or local network-layer filtering is in play.
30-day p50—samples—
DNSPod
119.29.29.29 · Tencent Cloud (China)
China-mainland focus
Tencent's mainland-China resolver.
DNSPod at 119.29.29.29 is Tencent Cloud's public DNS service. Similar profile to AliDNS — fast inside mainland China, slow from elsewhere — and similarly valuable as a second China-region data point for cross-checking how a record appears to Chinese users. Tencent and Alibaba run independent infrastructure, so when both return the same value it's strong confirmation; when they diverge, there's typically a recent change still propagating through mainland Chinese DNS infrastructure.
30-day p50—samples—
CleanBrowsing
185.228.168.9 · CleanBrowsing (US)
Global anycast (US-centric)
Optional family / adult-content filtering.
CleanBrowsing offers three free filtering profiles: security (blocks malware), adult (additionally blocks adult content), and family (additionally enforces SafeSearch on Google/YouTube/Bing). It's popular in US schools and homes for the family-filtering profile. Latency is best in North America. Good default for: parents who want a single DNS change to enforce SafeSearch across all devices without installing browser extensions or relying on each platform's parental controls.
30-day p50—samples—
Mullvad
194.242.2.2 · Mullvad VPN AB (Sweden)
EU + North America anycast
No-logs operator; DoH/DoT only (no plain UDP).
Mullvad DNS is run by the Swedish privacy-focused VPN operator. Unlike most public resolvers, Mullvad's DNS service only accepts encrypted queries (DNS-over-HTTPS or DNS-over-TLS); plain UDP queries on port 53 are not answered. Several blocking profiles exist: base (no filtering), adblock, family, extended. Best latency in Northern Europe. Good default for: users who already use Mullvad VPN, or anyone wanting an explicitly encrypted-only no-logs DNS service in Sweden's strict privacy jurisdiction.
30-day p50—samples—
ControlD
76.76.2.0 · Control D (Canada / global)
Global anycast
Customizable like NextDNS; built by Windscribe team.
Control D is run by the Windscribe VPN team and offers per-account customizable filtering similar to NextDNS. The free tier provides several pre-configured profiles (block malware, block ads, block social, etc.); paid tiers add custom blocklists, per-device routing, and detailed analytics. Performance is competitive with the bigger operators. Good default for: users who want NextDNS-style customization with a slightly different feature set and a Canadian/global infrastructure footprint.
30-day p50—samples—
Hurricane Electric
74.82.42.42 · Hurricane Electric LLC (US)
Global, infrastructure-heavy
Long-running ISP resolver; popular among network operators.
Hurricane Electric is best known as a major Tier 1 IP transit provider, but it also operates a public DNS resolver at 74.82.42.42. The resolver is more of a "network engineer's tool" than a mass-market service — there's no filtering, no fancy dashboard, just straightforward recursive DNS from one of the better-peered networks on the internet. Good default for: ISPs, hosting providers, and engineers who want a resolver from a deeply-peered transit operator as a reference point.
30-day p50—samples—
DNS4EU
86.54.11.1 · Whalebone / EU consortium
EU-only
EU-funded public resolver; GDPR-aligned by design.
DNS4EU is a publicly-funded European DNS initiative led by Whalebone, launched in 2025 to give EU users an alternative to US/non-EU public resolvers. It operates exclusively within EU jurisdiction, with explicit GDPR-aligned data handling and optional malware/phishing filtering. Latency is excellent inside the EU and meaningful elsewhere as a "what does this look like from an EU-jurisdiction resolver" data point. Still relatively new, so the POP footprint is smaller than the legacy operators.
30-day p50—samples—
Picking a resolver for your network
If you're configuring DNS for a household, small business, or single device, the realistic choices are: pick a fast one (Cloudflare, Google), pick a filtering one (Quad9, AdGuard, CleanBrowsing), or pick a customizable one (NextDNS, ControlD).
I just want fast DNS. Set primary 1.1.1.1, secondary 1.0.0.1. Add Google's 8.8.8.8 as a tertiary if your router supports three.
I want some malware/phishing protection without thinking about it. Set 9.9.9.9 (Quad9). The blocked-domain list is curated; false positives are rare.
I want network-wide adblocking. Set AdGuard (94.140.14.14) or NextDNS with an adblock profile. Test for a week — DNS-layer adblocking occasionally breaks sites that rely on tracker domains for functional content.
I want family-safe defaults. CleanBrowsing's family profile (185.228.168.168) blocks adult content and enforces SafeSearch. Or Quad9's 9.9.9.9 for security-only filtering without content restrictions.
I want detailed control + my own query logs. NextDNS or ControlD. Both have generous free tiers; both let you customize blocklists, see what your devices are querying, and route differently per device.
I'm an EU user who specifically wants EU-jurisdiction DNS. DNS4EU (86.54.11.1) is the explicit answer; Mullvad's Swedish resolver is the privacy-maximalist alternative.
Whichever you pick, configure two: a primary and a fallback from a different operator. If one operator has an incident (it happens — major public resolvers go down a few times a year), your DNS keeps working.
Cross-check any record across all 14
The leaderboard above tells you which resolvers are fast on synthetic test queries. To see how a specific record looks across all 14 right now, use the WhereIsDNS lookup tool: enter your hostname, pick the record type, and watch the answers stream in as each resolver responds.
Looking for resolver behavior under specific conditions? See the DNS Records guide for what each record type actually does, or the Glossary for terms like anycast, GeoDNS, and TTL that drive the patterns you'll see in the per-resolver results.