Eight DNS Providers Sort Into Exactly Two Camps, and the Line Is Sharper Than Anywhere Else in This Census

Every other 'premium vs. default' finding in this census has come from two, three, occasionally four vendors in one category. DNS providers give the same story with eight — and they agree on the direction more consistently than anything measured so far.

Eight providers, one line

Provider	Top 10K	10K-100K	100K-1M
NS16.43x top-heavy	2.43%	0.974%	0.378%
Akamai Edge DNS5.66x top-heavy	6.16%	2.436%	1.088%
Amazon Route 533.10x top-heavy	24.28%	17.564%	7.84%
Google Cloud DNS1.86x top-heavy	2.24%	1.606%	1.207%
Azure DNS1.67x top-heavy	1.76%	1.531%	1.057%
Cloudflare1.6x tail-heavy	23.48%	32.55%	37.208%
DigitalOcean5x tail-heavy	0.06%	0.274%	0.299%
GoDaddy6.25x tail-heavy	0.69%	2.199%	4.198%

Five providers climb from tail to top; three climb from top to tail. Not one of the eight breaks rank. NS1 and Akamai Edge DNS — both positioned as premium, traffic-engineering-grade DNS for companies that need fine control over routing and failover — post the two sharpest gradients in either direction. GoDaddy, the default DNS for anyone who registered a domain through GoDaddy and never touched the settings, posts the sharpest gradient of all, climbing more than sixfold from top to tail.

The domains behind the extremes confirm it

A spot-check of NS1's top-10,000 domains reads like a list of companies that specifically need enterprise-grade DNS traffic management: redhat.com, cnbc.com, mtv.com, salesforce-sites.com, ebaystatic.com, cengage.com (a major education publisher), pubmatic.com (ad-tech infrastructure), paylocity.com (payroll/HR). These are organizations where DNS failover and traffic routing genuinely matter at scale — not a default anyone falls into.

GoDaddy's deep tail looks like the mirror image: small nonprofits and community sites — beyondocd.org, howopen.org, a German data-protection-policy site, a Vietnamese community domain — the profile of someone who registered a domain years ago, pointed it at GoDaddy's default nameservers, and never had a reason to think about DNS again. Neither sample is cherry-picked to fit the story; it's what the two extremes of the same rank-tier gradient actually contain.

Closing a loop from earlier in this series

An early pass through this census flagged Cloudflare's DNS product as worth mentioning — "a third Cloudflare layer, alongside its CDN and bot-management shares" — but concluded it wasn't strong enough to stand as its own finding on its own terms. That conclusion was right at the time: Cloudflare's DNS number alone is just one data point, unremarkable in isolation. It only becomes a real finding once it's placed next to seven other DNS providers and the direction turns out to be consistent with every other free-tier default this census has measured (1.6× tail-heavy, the same direction as its own CDN product's 20.8%→42.2% climb in the original rank-tier post) — and once NS1, Akamai, Route 53, Google Cloud DNS, and Azure DNS all independently confirm the opposite end of the same line.

Limits, stated plainly

DNS provider detection here reads a response header, not homepage content, so it's a different and in some ways more reliable signal than most of this census — it's populated even for domains a homepage fingerprint can't otherwise reach. But it inherits the same rank-band caution as every other cut in this series: smaller providers (NS1, Azure DNS, Google Cloud DNS) have thinner absolute counts at the top of the list, so treat exact percentages as directional rather than decimal-precise. And as always, correlation isn't causation — a company doesn't get more traffic by switching to NS1; the more likely direction is that companies operating at real scale are the ones who find out they need enterprise DNS in the first place.

Query the full Tech Stack dataset

1,000,000 fingerprinted domains — CDN, DNS provider, CMS, ecommerce and more — over one REST API, ranked by Tranco traffic rank.

Explore the datasetPricing