Domain availability benchmark — dataset

Per-name registry availability for 15,018 candidate domains across 3 TLDs, measured 2026-08-02.

Download

• Per-name measurements (NDJSON) — one record per candidate domain checked: label, TLD, stratum, pattern, verdict, and sources.
• Aggregate + provenance (JSON) — capture date, method, registry endpoints, licence, credit line, known bias, and the by-stratum/by-pattern rollups behind the table below.

Results

Method

registry RDAP resolved via IANA bootstrap; 404=available, 200=registered, else indeterminate. A resolve pass re-checked 429-throttled names at 2s pacing; see resolvePasses.

Corpus frozen 2026-07-31 (version 1); measured 2026-08-02. 5,006 names across 3 TLDs — 15,018 checks in total, 0 unresolved.

The rest of this section describes the benchmark's method going forward, not this file: the capture above measured .com, .app, and .dev only, resolved through Verisign and Google Registry. Later runs widen coverage and add a control-probe safeguard the capture script did not yet have — described on /methodology , which always describes the benchmark's current method rather than this specific file's.

The 2026-08-02 capture above predates that control probe and ran without it. A wrong-but-real RDAP endpoint can answer a registered name with a well-formed 404 — indistinguishable from a genuine free-name response — so nothing in the resulting data could reveal such a failure after the fact.

The sampling frame — how the corpus is built, why it's frozen, and its known bias — is documented on /methodology .

Known bias

web2 is a dictionary, not a frequency list. The real-words and compounds strata over-represent archaic and obscure vocabulary, which is more available than common words. Read those two strata as an optimistic ceiling. Do not label them 'common English words'. A frequency-ranked list would fix this and needs sourcing.

The passage above is reproduced verbatim from the frozen corpus, including its own open item about needing a frequency-ranked list — we haven't rewritten it, because doing that would mean editing data inside a frozen, versioned file after the fact. It also says "real-words"; the corpus and this table call that same stratum dictionary-words.

The bias isn't confined to dictionary-words and compounds: every one of the 157 distinct bases the patterns stratum applies get-/try-/-hq-style prefixes and suffixes to is itself a dictionary-words word (getaalii, tryacetone, adonitehq — not typical startup vocabulary). Patterns rows are comparable with each other — one pattern scoring a few points ahead of another on the same TLD is a real finding — but their absolute availability rates inherit the same optimistic ceiling, and shouldn't be read as evidence that "a normal word with get-/try-/-hq" is generally this available.

832 of 15,018 checks (5.5%) were still unresolved after the capture script's inline retries — 419 on .app, 413 on .dev, none on .com — and were resolved across 2 paced re-check passes recorded in resolvePasses, leaving 0 unresolved. One registry throttled that run and the other did not.

Licence

The measurements and this compilation are released under CC BY 4.0. Please credit: Domain Yoga — https://domain.yoga/data/availability. The licence covers our measurements and their compilation, not the underlying wordlist, which is Webster’s Second (1934) and in the public domain.

Cite this dataset

Domain Yoga (2026). Domain availability benchmark [Data set]. Captured 2026-08-02, measured through 2026-08-03 via resolve passes. https://domain.yoga/data/availability. Licensed under CC BY 4.0.