DNS lists 30 providers and Amazon Route 53 scores below its own resolver

DNS lists 30 providers and Amazon Route 53 scores below its own resolver

The DNS area on apis.io lists 30 providers. For a part of the stack that most developers set up once and rarely touch again, the scores are high: 16 of the 30 score strong or exemplar, 13 score developing, and only one scores thin. No provider in the area is in the emerging or minimal bands.

One detail first: the area’s frontmatter has a provider_count of 59, but the page’s overview and its provider list both show 30. This post uses the 30 it can name.

Standouts by band

Band Provider Kin Score APIs
Exemplar Cloudflare 80.6 26
Exemplar WhoisFreaks 67.1 1
Strong cPanel 65.2 3
Strong Cisco Umbrella 62.7 52
Strong DomScan 62.1 4
Strong Amazon Route 53 Resolver 55.7 1
Strong Google Cloud DNS 54.3 1
Developing Infoblox 47.3 1
Developing Amazon Route 53 46.8 1
Developing CoreDNS 39.6 2

What the area tells you

Authoritative DNS is not what leads. Amazon Route 53, AWS’s hosted-zone service, scores 46.8 (developing). Amazon Route 53 Resolver, the VPC-side service that forwards queries, scores 55.7 (strong). Google Cloud DNS scores 54.3. Each is listed as one API, so the gap is not breadth. It is how much of each record the catalog can verify.

Lookup services score as well as infrastructure. WhoisFreaks (one API, 67.1) and DomScan (four APIs, 62.1) sell answers about domains, not resolution. They score above most of the platforms that run resolvers. Domain intelligence is a data product, and data products tend to document themselves.

Enterprise DNS sits in the middle. Infoblox, the DDI incumbent, scores 47.3 on a single API. Cisco Umbrella, a DNS-layer security product, scores 62.7 across 52 APIs, second in breadth only to the APIFreaks hub’s 127. For a DNS-layer security product, the resolver is the product, and Umbrella publishes a lot about it.

Cloudflare is the ceiling. It scores 80.6 across 26 APIs, and it is the only infrastructure provider in the exemplar band. It is the reference point for a DNS provider that wants agents to be able to manage zones.

Takeaway

DNS is one of the better-documented areas in the catalog, with no long tail of minimal providers. Its unevenness is between products from the same company, not between companies. If you automate DNS on AWS, the Resolver record is in better shape than the Route 53 record next to it. See the full area at apis.io/areas/dns/ and the research at dns.apievangelist.com.

← The Dataverse MCP server now calls Custom APIs as one transaction
Shodan's Network Alerts API updates with POST and sends its key in the query string →