Say you run the infrastructure for a small team on AWS. Last month you set up your hosted zones once, and you have barely thought about them since. Now someone wants an agent to help manage DNS, and you need to know which services are documented well enough for that to work. You open the DNS area on apis.io to see what the catalog can tell you.
The first thing you notice is a mismatch. The area's frontmatter says it has 59 providers, but the overview and the provider list both show 30. The post you're reading uses the 30 it can actually name, and so will you.
Then the scores. For a part of the stack that most developers set up once and rarely touch again, they are high. Of the 30 providers, 16 score strong or exemplar, 13 score developing, and only one scores thin. Nobody in the area lands in the emerging or minimal bands. There is no long tail of poorly documented providers to wade through.
At the top sits Cloudflare, an exemplar at 80.6 across 26 APIs. It is the only infrastructure provider in that band, which makes it the reference point for a DNS provider that wants agents to be able to manage zones. The other exemplar is WhoisFreaks at 67.1 with a single API. Below them, in the strong band, come cPanel at 65.2, Cisco Umbrella at 62.7, DomScan at 62.1, Amazon Route 53 Resolver at 55.7 and Google Cloud DNS at 54.3.
Some of that is not what you'd guess. Lookup services score as well as infrastructure. WhoisFreaks and DomScan, which has four APIs, sell answers about domains rather than resolution, and they score above most of the platforms that run resolvers. The post's reading is that domain intelligence is a data product, and data products tend to document themselves. Cisco Umbrella, a DNS-layer security product, scores across 52 APIs, second in breadth only to the APIFreaks hub's 127. The post's explanation is that for a security product the resolver is the product, so Umbrella publishes a lot about it. Infoblox, the DDI incumbent, sits in the middle at 47.3 on one API.
Now you look for the thing you came for. Amazon Route 53, AWS's hosted-zone service, scores 46.8, which is developing. Right next to it, Amazon Route 53 Resolver, the VPC-side service that forwards queries, scores 55.7, which is strong. Google Cloud DNS, for comparison, scores 54.3. Each of these is listed as one API, so the gap is not about breadth. The post says it comes down to how much of each record the catalog can verify.
This is the turn in the story, and it is a turn against a big name. Authoritative DNS, the service most people picture when they think of DNS on AWS, is not what leads the area. The company's resolver record is in better shape than its zone-hosting record, and the lower of the two is the one you were about to build on.
That is also a useful correction to how you might have been thinking about this. You may have assumed the differences would be between companies, with some vendors good at documentation and others not. The post says the unevenness here is between products from the same company. A single provider name tells you less than you'd expect.
So what do you take away? DNS is one of the better-documented areas in the catalog, and you can choose among its providers without worrying about a tail of minimal ones. But if you automate DNS on AWS, don't assume the two Route 53 products are equally well described. The Resolver record is the stronger one, and the Route 53 record next to it is the one where you should expect to verify more yourself. The score reflects how much of each record the catalog can verify, which is a statement about the record, not a verdict on the service.
Read the original: https://apis.io/2026/11/13/dns-lists-30-providers-and-amazon-route-53-scores-below-its-own-resolver/