.passkey
Is .passkey a real TLD? Who’s applying to run it?
Nobody has applied for .passkey in its own right, as of 7 October 2026. GoDaddy Registry named .passkey as the replacement string of its .agentid application.
A narrow security-term namespace: useful for passkey-related microsites and tooling, rarely a company's main address.
identity and security vendors, authentication tooling projects, and developer-facing passkey services wanting a descriptive address for a login product, demo, or documentation site
No applications recorded for this TLD yet.
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.
Like .passkey, it is a plain consumer word for an authentication credential rather than a market or industry, so the bet is that a generic token-of-access noun can be owned as a namespace by whoever controls the mechanism it names.
Same bet shape as .passkey: a trust-assertion string whose value exists only if the registry enforces rules behind it, since an unenforced promise of security on the right-hand side is worth nothing to the party putting its login identity there.
It is the broad industry-category noun adjacent to the target, but its primary identity holders would be security vendors advertising a sector, whereas .passkey names one specific credential mechanism and would be claimed by whoever stewards that standard.
What a .passkey domain is
.passkey is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. Nobody has applied for .passkey in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .passkey domain extension real yet?
.passkey 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 .passkey domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .passkey name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .passkey was .pin, delegated on 5 December 2015.
Is .passkey a real TLD?
Not yet. .passkey is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .passkey as part of an application for another string. Every entry on this page links to its source.
- GoDaddy Registry · first recordedICANN
“NA2631T-T41814 · Registry Services, LLC · replacement string of .agentid”ICANN
“LFGL2683T-T82030 · Link Freedom Group Ltd · primary NA2631T-T80151 · Registry Services, LLC · replacement string of .all · Deactivated”ICANN
- Band chosen: 10-29 (vanity/narrow). The string names a single credential technology (passwordless login keys), not a category of business, so the natural buyer pool is identity and security vendors plus developer tooling, and most of those already carry an established brand on a mainstream TLD; a .passkey address would typically be a product microsite, a demo, or a defensive registration rather than a primary identity. By analogy (flagged as analogy), feature-word TLDs such as .email, .security and .cloud found registrants but produced weak brand signal and thin aftermarkets, and .passkey is narrower than any of those. It is not in the 30-49 band because registrations at volume are unlikely: the term describes something a site offers, not what a project is, so even price-driven demand should stay small. It is not in the 1-9 band because passkeys are a live, growing authentication standard with real vendor marketing budgets, and a major registry operator is on the record for the string (as a replacement string of .agentid, per the verified facts), which supports a credible launch and channel distribution. Main market uncertainty: whether the operator positions .passkey as an infrastructure namespace for identity services (addresses that authentication systems reference programmatically) rather than a vanity marketing TLD; infra adoption by a few identity providers could lift it into the 30-49 band, while pure marketing use keeps it where scored. Figures on comparable TLD registration counts are unknown here and are not asserted.