ActorStack.dev
ActorStack.dev
Domain and DNS intelligenceMeasured

1.62% of registered .com domains are missing from the zone file

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.

By Oswaldo Carabano6 min read
A white measuring tape curving across a dark background, showing the numbers 15 to 45.
Photo: Semanur Çoban on Pexels

Short answer

A domain absent from a registry zone file is usually unregistered, and about 1.62% of the time it is registered anyway — suspended, newly bought, or simply with no nameservers set. The figure comes from comparing ICANN's monthly registry reports against the zone itself: 169,209,254 `.com` domains registered against 166,467,808 present in the zone. The rate is not uniform, running at roughly 2.4% in `.net` and 3.1% in `.org`, so a screening verdict is a little weaker outside `.com` than inside it. Publishing the rate rather than the verdict alone is what turns a guess into a measurement somebody can plan around.

Key points

  • About 1.62% of registered `.com` domains are absent from the zone file at any given time, which is the exact error rate of a 'probably free' verdict there.
  • The figure comes from ICANN's monthly registry reports — 169,209,254 `.com` domains registered against 166,467,808 in the zone — rather than from an estimate.
  • A registered domain can be absent because it is suspended, newly bought, or has no nameservers set, and none of those states is visible from the zone.
  • The rate runs at roughly 2.4% in `.net` and 3.1% in `.org`, so the same verdict carries roughly twice the error outside `.com`.
  • Presence in the zone has no equivalent error rate, because delegation is the registry's own record rather than an inference from it.
  • A screening tool that publishes its error rate can be planned around, and one that publishes only a verdict cannot.
On this page5 sections

Two verdicts, unequal strengths, and one of them has a number attached.

Why the two answers differ in strength

Presence in a zone file is a positive fact: the registry delegated this name. Absence is the absence of a fact, and absences are always weaker — a domain can be registered and missing from the zone, and nothing in the zone can say so.

Measuring the gap against ICANN's own reports

The size of that weakness was not guessed. ICANN publishes monthly registry reports with per-TLD domain counts, and comparing one against the zone gives the gap directly:

Measure.com
Registered, per ICANN's registry reports169,209,254
Present in the zone file166,467,808
Registered but absent1.62%

Why a registered domain goes missing

Because delegation and registration are different states. A domain can be registered with no nameservers set at all — freshly bought and not yet configured, or parked in a registrar account with nothing pointing anywhere. A suspended domain may have its delegation pulled while the registration stands. None of those are visible from a file that only records delegation.

The rate is not the same everywhere

Roughly 2.4% in .net and 3.1% in .org, against 1.62% in .com. A probably_free verdict therefore carries about twice the error outside .com as inside it, which is worth knowing before a shortlist is filtered on it.

Planning around a published error rate

Frequently asked questions

Can a registered domain be missing from the zone file?
Yes, and about 1.62% of registered `.com` domains are at any given time. A domain that is suspended, newly bought or simply has no nameservers set is registered and absent from the zone, and none of those states is distinguishable from unregistered by looking at the zone.
Where does the 1.62% come from?
From ICANN's monthly registry reports compared against the zone file itself: 169,209,254 `.com` domains registered against 166,467,808 present in the zone. It is a comparison of two published counts rather than a sampled estimate.
Is the error rate the same in every TLD?
No. It runs at roughly 2.4% in `.net` and 3.1% in `.org` against 1.62% in `.com`, so a 'probably free' verdict carries about twice the error outside `.com` and should be treated accordingly.
Does 'taken' have an error rate too?
No, because it is not an inference. A 'taken' verdict means the domain is delegated in the registry's own zone file, which is the registry's record of what exists rather than a conclusion drawn from an absence.

Sources

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

  1. Law or regulatorchecked 18 Sept 2026
    Registry Reports — monthly per-TLD transaction and domain countsICANN
  2. Operator claimchecked 18 Sept 2026
    Bulk Domain Search — Actor README and input schemaActorStack / Apify Store
  3. Law or regulatorchecked 18 Sept 2026
    EPP Status Codes — What Do They Mean, and Why Should I Know?ICANN

Related reading

A white shuttered window on a peach-coloured building with a for-sale notice beside it.
DomainsGuide

Bulk availability without WHOIS

Screening a naming shortlist against zone files instead of querying WHOIS per name: what it costs, what the verdicts mean, and where the method stops being enough.

7 min
Racks of network equipment in a dimly lit server room, lit blue by their indicators.
DomainsMeasured

What dns_provider can tell you

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.

5 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