.check
Is .check a real TLD? Who’s applying to run it?
.check is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Identity Digital. XYZ named .check as a backup string for its .fab application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup. GoDaddy Registry named .check as a backup string for its .form application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A readable generic word that fits verification and status tools, but verb-style endings rarely become a serious brand's main address.
verification, compliance, fact-checking and uptime/status services wanting a phrase-like address (fact.check, health.check), plus domain-hack buyers
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .form application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .fab application, shown as deactivated: another applicant applied for the same string or named it as a backup
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet as .check: a bare generic English verb naming the step a consumer takes before deciding, so its value rests entirely on whether a registry can make "<thing>.compare" read as an instruction rather than as somebody's brand — the identical open-generic-vs-closed-generic fork .check faces.
Like .check, the whole product is the attestation the right-of-dot word confers on whoever registers it, so both are worth only what the operator's gatekeeping and policing are worth, not what the word means.
Another plain verb-noun of evaluation bought as a volume keyword rather than as an identity: anyone verifying, rating or vetting something is the buyer, and neither string has a defined community or profession that owns it.
What a .check domain is
.check is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. One application for it is on ICANN’s Reveal Day list.
Is the .check domain extension real yet?
.check is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .check domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .check name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .check was .compare, delegated on 15 January 2016.
Is .check a real TLD?
Not yet. .check is not in the DNS root, so nothing resolves under it. It’s here because .check is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
“NA2631T-T90582 · Registry Services, LLC · replacement string of .form · Deactivated TCL2632T-T19690 · Tidal Case, LLC · primary XL2625T-T84175 · XYZ.COM LLC · replacement string of .fab · Deactivated”ICANN
- Band chosen: 30-49, usable but limited. The string is a common English word with several live meanings (verify, tick-mark, payment check, checkout, status check), so phrase-style registrations such as fact.check, background.check, spell.check or health.check read naturally and should see steady registrations at volume or on price. By analogy only, delegated verb/action endings such as .click, .link, .watch and .review have tended to draw registrations but little primary-identity use by serious projects and thin aftermarkets, and .check sits in that family. It is not in the 50-69 band because no single category treats 'check' as its namespace: verification and compliance vendors, fact-checkers and status-page tools each have established alternatives on legacy endings and would need to explain the choice. It is not in the 10-29 band because the word is broad, non-jokey and useful across verification, finance and software, giving it more than event-driven or novelty demand. The record shows one application from Tidal Case, LLC with status confirmed; the operator's background, pricing and distribution plans are unknown, so adoption likelihood is reasoned from the string alone. Main market uncertainty: whether the analogy to prior verb endings holds, or whether verification, fraud-prevention and status-monitoring vendors adopt it as a category convention over the next 5 years; registrar pricing and channel reach are also unknown.