Black Friday. Up to 25% extra credits.See packs

.passkey

Is .passkey a real TLD? Who’s applying to run it?

Nobody has applied for .passkey in its own right, as of 18 November 2026. GoDaddy Registry named .passkey as a backup string for its .agentid application. ICANN’s list shows it as deactivated: the application cannot move to it.

AI & tech · on the record since Oct 7, 2026, updated Nov 18, 2026
applicants
0 applications · 1 deactivated backup

Nobody has applied for .passkey in its own right.

backups
  • The applicant kept its .agentid application and did not switch to this replacement (backup) string: shown as deactivated on the ICANN String Confirmation Day list, 17 November 2026

    named as replacement for .agentid Oct 7, 2026 · named as a backup for .agentid, deactivated by ICANN Nov 17, 2026

    Deactivated backup for .agentidGenericICANN NA2631T-T41814ICANN ↗

Will names sell?

◈AI score
27/ 100
Vanity and narrow

A narrow security-term namespace: useful for passkey-related microsites and tooling, rarely a company's main address.

assessed by claude-fable-5-1 · Oct 7, 2026

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. .passkey’s closest 2012 strings hold .pin 2, .secure 2 and .security 931.

AI score 27 of 100. .com scores 96, .ai scores 84.

For comparison, .com scores 96 and .ai scores 84 on the same rubric.

How the AI’s blind 2012 read held up: its score of each 2012 string against the names it holds today808 2012-round TLDs. Scored 60 or more: median 27168 names. Scored under 30: median 30 names. .passkey's closest 2012 strings: .pin scored 35, 2 names; .secure scored 55, 2 names; .security scored 56, 931 names.101001K10K100K1M020406080100scored 60+: median 27Kunder 30: median 30.pin · 35 · 2.secure · 55 · 2.security · 56 · 931the AI’s blind 2012 score of each string (its own scale) →names held today (log) →

a 2012-round TLD.passkey’s closest 2012 strings: score · names

The 2012 read is a separate, time-locked score on its own scale, so .passkey’s score above is not placed on it. Names: the registries’ reports to ICANN, 2026-10. Non-brand 2012 TLDs in the root.

closest 2012 strings
3 of 1,408

The nearest 2012 strings, and how many names each holds today

The closest 2012 string, .pin, held 2 names, June 2026. .secure held 2; .security held 931. Chosen by AI from every string in the 2012 round, without being told what happened to any of them.

  1. .pinmoderate2 names, June 2026live since 2015 · uncontested in 2012 · scored 35* in 2012 · Amazon EU S.à r.l.See .pin in Stats

    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.

  2. .securemoderate2 names, June 2026live since 2016 · 2 applications in 2012 · scored 55* in 2012 · Amazon EU S.à r.l.See .secure in Stats

    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.

  3. .securityweak931 names, June 2026live since 2015 · 3 applications in 2012 · scored 56* in 2012 · Symantec CorporationSee .security in Stats

    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.

Names are from the registries’ monthly reports to ICANN. Each name opens the TLD’s stats page: how it grew, who sells it, and the 2026 strings compared with it. * A separate 2012-only read, time-locked to what was public that year, on a different scale from this page’s score.

who it’s for

identity and security vendors, authentication tooling projects, and developer-facing passkey services wanting a descriptive address for a login product, demo, or documentation site

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, in our AI & tech category. 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. A .passkey 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 .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.

Considering a name on .passkey?Appraise a name on this TLD →

This record is corrected in the open. See the changelog and methodology.