.status
Is .status a real TLD? Who’s applying to run it?
.status is not contested. One application for it is on ICANN’s Reveal Day list, as of 18 November 2026. It is Bytex Digital UG (haftungsbeschränkt). Mux Registry named .status in its .list application, and withdrew that application.
Who is applying, and what they run today
Will names sell?
A narrow utility name for uptime and service-status pages; useful as a secondary address, rarely anyone's main identity.
Last round the AI scored the 2012 strings blind to their fate. Strings it scored 60 or more hold a median 27,168 names today; those under 30, a median of 30. .status’s closest 2012 strings hold .help 225K, .support 43K and .contact 12K.
The nearest 2012 strings, and how many names each holds today
The closest 2012 string, .help, held 225,417 names, June 2026. .support held 43,314; .contact held 12,039. Chosen by AI from every string in the 2012 round, without being told what happened to any of them.
Same bet as .status: an abstract functional noun that almost nobody uses as a business identity, sold on the premise that organizations will lift a standing operational surface (help.brand.com) out to the right of the dot, so the registry's demand is a per-company utility label rather than a category of registrant.
Like .status it is a service-desk function word whose buyer is an existing brand relocating one of its own customer-facing surfaces, meaning the string's worth depends on companies treating a TLD as infrastructure naming instead of as a market they compete inside.
Also a pure channel-label noun with no community or trade behind it — the same wager that a functional page every company already runs becomes a domain — but it is addressed to the whole web rather than to the narrower operational/engineering audience that gives .status its pull.
software and SaaS teams wanting a memorable public uptime or service-status page, plus a smaller slice of hosting and infrastructure providers
What a .status domain is
.status is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Infrastructure category. One application for it is on ICANN’s Reveal Day list.
Is the .status domain extension real yet?
.status 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 .status domain?
You can’t yet. A .status name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .status was .help, delegated on 16 August 2014.
Is .status a real TLD?
Not yet. .status is not in the DNS root, so nothing resolves under it. It’s here because .status is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
“BDUH2620T-T63426 · Bytex Digital UG (haftungsbeschränkt) · primary MRL2648T-T18053 · Mux Registry L.L.C-FZ · replacement string of .list · Deactivated”ICANN
“BDUH2620T-T63426 · Bytex Digital UG (haftungsbeschränkt) · primary”ICANN
“BDUH2620T-T63426 · Bytex Digital UG (haftungsbeschränkt) · primary MRL2648T-T18053 · Mux Registry L.L.C-FZ · replacement string of .list · Deactivated”ICANN
- Band chosen: 10-29 (vanity/narrow). The string has one clear, recurring real-world job — the public status page that software and infrastructure companies publish for outages and uptime — so demand is genuine but entirely secondary: a company's primary identity stays on its main domain, and .status would at most be a pointer to one page. The dominant convention for that page today is a subdomain on the company's own domain (status.example), which costs nothing and carries the brand, so a paid TLD has to displace a free habit; by analogy (flagged as analogy) with other single-purpose descriptive strings such as .support, .help and .page, such strings have tended to see modest registration volumes, little primary-identity use and a thin aftermarket, which is why this is not in the 30-49 band: I do not expect volume-driven registrations or price-driven churn, just a small base of deliberate utility buyers. It is above the 1-9 band because the use case is concrete, global, and recurring every time a SaaS product launches, and a registrar or status-page vendor could package it as a product. On the record, one standard application is confirmed (Bytex Digital UG) and a second (Mux Registry) is deactivated; a related .uwu application from the same applicant naming .status as primary is also deactivated — these are neutral facts about the applicant pool, not the market. Main market uncertainty: whether any status-page or uptime-monitoring vendor adopts .status as the default hostname it hands customers, which would convert the string from a vanity choice into a convention; absent that, adoption stays a trickle. Specific figures for comparable TLDs are unknown to me within the verified facts, so all comparisons are qualitative.