.entity
Is .entity a real TLD? Who’s applying to run it?
Nobody has applied for .entity in its own right, as of 7 October 2026. Suffix named .entity as the backup string of its .asap application.
An abstract word with no clear buyer group; a few brands may pick it for flavor, but it is unlikely to become anyone's default address.
small brands, studios and AI-agent or digital-identity projects that want an abstract, slightly formal-sounding name; occasional legal-structure or registered-agent services
Nobody has applied for .entity in its own right.
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: a bare, formal umbrella noun for an organization as a legal body, open to any incorporated buyer, whose value rests entirely on firms wanting a registry that signals official corporate standing rather than a market or audience.
Same buyer and the same generic-organizational-noun job, but it is an everyday commercial word with self-evident appeal where .entity is the colder abstraction, so the demand assumption behind it is far easier to satisfy.
Same underlying wager that a firm will put its primary identity on its legal form rather than on what it sells, though it names one specific statutory form instead of the abstract category covering all of them.
What a .entity domain is
.entity is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Brand category. Nobody has applied for .entity in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .entity domain extension real yet?
.entity is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .entity domain?
You can’t yet. A .entity name can only be registered once the string is delegated (added to the DNS root) and its registry opens.
Is .entity a real TLD?
Not yet. .entity is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .entity as part of an application for another string. Every entry on this page links to its source.
- Suffix · first recordedICANN
“SI2639T-T21581 · Suffix Inc. · replacement string of .asap”ICANN
- Band chosen: 10-29 (vanity/narrow), near the top of it. The string is a generic abstract noun that names no product, place, profession or activity, so it does not describe what a site is; its strongest associations are legal structure ("legal entity"), data/NLP ("named entity") and, more recently, AI agents or digital beings described as entities. It is not in the 30-49 band because there is no evident volume driver: by analogy, business-structure strings such as .company, .business, .inc, .llc and .ltd have either needed heavy discounting or stayed small, and .entity is vaguer than any of them, so even price-driven volume looks unlikely (analogy, not a figure). It is not in the 1-9 band because the word is short, pronounceable, English-common and carries a mildly formal, sci-fi flavor that a handful of studios, agent frameworks or identity projects could plausibly adopt as a primary identity, and a few dictionary-word-plus-.entity combinations would be memorable. On the record the only application is Suffix Inc.'s, filed as a replacement string for .asap, which suggests it is a fallback rather than a primary portfolio bet; this is stated neutrally and bears only on how aggressively the string would be marketed. Main market uncertainty: whether "entity" becomes an accepted shorthand for AI agents or on-chain identities over the next five years, which would create a real, if niche, primary-identity use case and could lift the string into the 30-49 band; absent that, demand stays shallow and brand-driven.