.agentid
Is .agentid a real TLD? Who’s applying to run it?
.agentid is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is GoDaddy Registry.
A technical label for AI-agent identities, not a brand suffix; useful only if an agent-identity standard adopts it.
builders of AI-agent platforms and identity/credential infrastructure who want a machine-readable namespace for naming and verifying autonomous agents, plus a few speculators riding the agent hype
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: carve a namespace for a brand-new class of non-human software entity whose operator, not a consumer, does the registering, and whose value depends entirely on client software agreeing to treat that suffix as meaningful.
Same bet that the namespace's worth comes from the registry's vetting rather than the word itself — registrants are buying a verifiable assertion about who they are, which is exactly what an identifier suffix has to sell.
Same platform-owner bet that a new software category will adopt one suffix as its default address space, where success requires an ecosystem to standardize on it rather than individual buyers liking the word.
What a .agentid domain is
.agentid is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our AI & tech category. One application for it is on ICANN’s Reveal Day list.
Is the .agentid domain extension real yet?
.agentid 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 .agentid domain?
You can’t yet. A .agentid 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 .agentid was .bot, delegated on 5 December 2015.
Is .agentid a real TLD?
Not yet. .agentid is not in the DNS root, so nothing resolves under it. It’s here because .agentid is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- GoDaddy Registry · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The string is a compound technical descriptor ("agent id"), and an address like acme.agentid reads as an identifier rather than a primary identity a serious project would lead with; that keeps it below the 30-49 band, where registrations at least happen at volume or on price with a recognizable if weak brand signal. It sits above the 1-9 band because identity for autonomous AI agents is a genuinely emerging need over the next 5 years (agent authentication, delegation, verifiable credentials), and a registry could plausibly run the namespace as structured, issued identifiers rather than open vanity registrations. By analogy (flagged as analogy), single-purpose descriptive strings aimed at a machine-facing use case such as .bot have seen limited primary-identity adoption and thin aftermarkets even with real underlying activity; compound descriptors have historically fared worse than their short root words. The record shows one confirmed application by Registry Services, LLC, and a sibling .passkey application by the same applicant naming .agentid as its primary, which suggests an identity-infrastructure positioning rather than a consumer brand play; that would inform adoption likelihood if the namespace is bundled into agent tooling, but would mostly produce issued identifiers, not tradeable names. Main market uncertainty: whether agent-identity standards converge on DNS-based namespaces at all, versus DIDs, platform-internal registries, or existing TLDs such as .ai, and whether anyone would pay a premium for the string rather than treat it as plumbing.