ActorStack.dev
ActorStack.dev
Domain and DNS intelligenceMeasured

A nameserver names the DNS operator, not the technology behind the site

The nameserver identifies who runs the DNS for 69.1% of domains. It does not identify what a site is built with, and the measurement that settled that question is worth seeing.

By Oswaldo Carabano5 min read
Racks of network equipment in a dimly lit server room, lit blue by their indicators.
Photo: panumas nikhomkhai on Pexels

Short answer

A domain's nameserver identifies the organisation running its DNS, and across every domain in the zone that inference succeeds on 69.1% of them. What it does not identify is what the website is built with. A domain on Cloudflare can be running anything at all, because website platforms are configured through A and CNAME records that a zone file does not contain. The measurement that settled it: Shopify is visible on 185 domains out of 64 million examined, which is not a technology detection rate but an accident of a handful of merchants pointing nameservers somewhere unusual. A column that looked impressive was dropped in favour of one that is true.

Key points

  • A nameserver identifies the organisation running a domain's DNS, and that inference succeeds on 69.1% of domains measured across the whole zone.
  • The remaining 30.9% delegate to nameservers that match no known operator, so the field is empty rather than guessed.
  • Website platforms are configured through A and CNAME records, which registry zone files do not contain, so a platform cannot be inferred from delegation.
  • Shopify was visible on 185 domains out of 64 million examined, which measures an accident rather than a technology footprint.
  • A domain on Cloudflare can be running anything at all, so treating `dns_provider` as a tech-stack signal produces confident and wrong conclusions.
  • Shipping a column that is true instead of one that looks impressive is the decision the 185-domain measurement forced.
On this page5 sections

A column that looks impressive and a column that is true were, in this case, two different columns.

What the field actually infers

dns_provider reads the nameserver hostname and names the organisation running that domain's DNS. ns1.digitalocean.com is DigitalOcean. That is a hosting fact about where DNS is answered, and it is the entire claim.

Why 69.1% and not more

Measured across every domain in the zone, the nameserver identifies a known operator on 69.1% of them. The other 30.9% delegate to hostnames that match nothing recognisable — a self-run server, a small host, a name that identifies no one. The field is left empty there. Filling it with a guess would have raised the coverage number and lowered the value of every row.

Why it is not a technology signal

Because a website platform is configured through A and CNAME records, published by the domain's own nameservers — and a registry zone file contains neither. A domain on Cloudflare can be running anything at all. Cloudflare is DNS, not a stack.

The measurement that ended the argument

Using the field for what it is good at

Separating shared infrastructure from dedicated infrastructure, which is exactly what makes a nameserver pivot readable; spotting a delegation that moved to a parking service; and grouping a portfolio by who actually runs its DNS. All hosting questions, all answerable, none of them about what a site is built with. The same discipline governs how the DNSSEC rate is published.

Frequently asked questions

What does dns_provider tell me?
It names the organisation running the domain's DNS, inferred from the nameserver hostname, and it is filled on 69.1% of domains. That is a hosting fact about where DNS is answered, and it is the only thing the field claims.
Can I tell what platform a site runs on?
Not from zone data. Website platforms are configured through A and CNAME records published by the domain's own nameservers, and a registry zone file contains neither, so any platform column built on delegation would be a guess.
Why is the field empty on 30.9% of rows?
Because those domains delegate to nameservers that match no known operator — a self-run server, a small host, or a name that identifies nothing. Leaving the field empty is the accurate answer, and filling it with a guess would not be.
What did the Shopify measurement show?
Shopify appeared on 185 domains out of 64 million examined, which is far too few to be a platform footprint. It measured a handful of merchants with unusual nameserver setups, and it is why a platform column was never shipped.

Sources

Every URL below was requested and returned a page on the date shown.

  1. Operator claimchecked 18 Sept 2026
    Reverse Nameserver Lookup — Actor README and input schemaActorStack / Apify Store
  2. Platform docschecked 18 Sept 2026
    RFC 1035 — Domain Names: Implementation and SpecificationIETF
  3. Operator claimchecked 18 Sept 2026
    Typosquatting Detection — Actor README and input schemaActorStack / Apify Store

Related reading

A white measuring tape curving across a dark background, showing the numbers 15 to 45.
DomainsMeasured

Probably free, not available

Absence from a zone file usually means unregistered, and sometimes does not. The gap was measured against ICANN's own monthly registry reports rather than estimated, and it differs by TLD.

6 min
A white measuring tape curving across a dark background, showing the numbers 15 to 45.
DomainsMeasured

DNSSEC adoption by TLD

Measured across the whole zone, 5.0% of domains publish a DS record. Per registry the rate runs from 0% to 100%, which is what makes the global figure unusable on its own.

5 min
A shelf of office binders with dated labels along their spines.
DomainsComparison

Passive DNS versus zone files

Two sources that look interchangeable for infrastructure questions and answer differently shaped questions. Which one to reach for depends on whether you need history, resolution or completeness.

6 min