.hubid
Is .hubid a real TLD? Who’s applying to run it?
.hubid is not contested. One application for it is on ICANN’s Reveal Day list, as of 18 November 2026. It is Hub Culture.
Who is applying, and what they run today
Will names sell?
A made-up word with no clear meaning; useful mainly inside one company's own ecosystem, not as a general web address.
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. .hubid’s closest 2012 strings hold .comsec 2.
The nearest 2012 strings, and how many names each holds today
The closest 2012 string, .duns, held 2 names, August 2019. .comsec held 2. Chosen by AI from every string in the 2012 round, without being told what happened to any of them.
Same bet: a proprietary identifier scheme turned into a namespace, where the value comes from one operator being accepted as the issuer of record for everyone else's machine-readable identity rather than from any pool of registrants who would call themselves this.
- .mitek
Same bet in brand form: a coined two-morpheme tech compound owned by a single identity-verification vendor, so the string's only plausible primary identity is the operator's own platform and its enterprise integrations, never a self-describing category.
Shares the construction and the register — clipped infrastructure jargon welded into one word, read as a trust/security function but controlled by one firm — yet it stakes a security claim rather than an identity-issuance claim, and nothing in 2012 bet on a credential hub as a market.
members and projects inside the applicant's own community or identity platform, plus a handful of speculators chasing short "id"-style handles
What a .hubid domain is
.hubid is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Brand category. One application for it is on ICANN’s Reveal Day list.
Is the .hubid domain extension real yet?
.hubid 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 .hubid domain?
You can’t yet. A .hubid 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 .hubid was .duns, delegated on 23 July 2016.
Is .hubid a real TLD?
Not yet. .hubid is not in the DNS root, so nothing resolves under it. It’s here because .hubid is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Band chosen: 10-29 (vanity/narrow), at its floor. The string is a coined compound — "hub" plus "id" — with no dictionary meaning, no category tag on the record, and no natural buyer group searching for it. On the record it is a replacement string (a fallback to the applicant's primary .hub application) filed as a standard, not brand, application by HUB Culture Ltd, which suggests its most plausible use is as an identity or membership namespace within that applicant's own ecosystem rather than as an open-market address. By analogy (flagged as analogy): coined strings without semantic anchor have historically relied on registrar promotion or free/near-free pricing to show volume, and such volume has tended to be shallow and non-renewing; the exceptions that gained traction did so through aggressive marketing and brevity, which a five-letter, two-syllable-plus-suffix string does not share. It is not in the 1-9 band because a closed or semi-closed identity use (handle.hubid for community members) is a realistic, if small, market and could see sustained use inside one platform. It is not in the 30-49 band because there is no evidence of volume demand, no price lever on the record, and the string carries no brand signal to an outside audience — a serious project would need to explain it every time. Main market uncertainty: whether the applicant operates it as an open registry marketed to the public (which would test whether "id"-suffixed handles find any demand) or as a mostly internal namespace; the latter is the more likely reading of a standard-type replacement string.