.lock

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

.lock is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Identity Digital.

Generic application · AI & tech · on the record since Oct 7, 2026, updated Oct 7, 2026
applicants
1 application

Who is applying, and what they run today

Identity Digital filed 216 applications across the round.

  • Acid Medal, LLC

    Identity Digital

    controlled by Ethos Capital Digital Infrastructure UGP LLC

    277 TLDs · 14.80M names: .info 5.63M, .pro 1.25M, .live 672K

    backup .wire, disallowed

runs TLDs today; the larger, the more namesruns none.tld in orange: one of this string’s closest 2012 stringsbackup .x usable · backup .x ✕ disallowed

Applications are counted by company, across its legal entities, from ICANN’s list. Names are from the registries’ June 2026 reports to ICANN. “None on record” means no public source in our record ties the company to a registry operator that runs TLDs today. Control: each application’s own answer to ICANN (question 108). Largest TLDs and names: the registries’ monthly reports to ICANN.

Will names sell?

◈AI score
34/ 100
Usable but limited

A short security-flavored word that fits locksmiths, smart-lock makers and token-locking tools, but few would make it their 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. .lock’s closest 2012 strings hold .safe 2, .locker 9K and .secure 2.

AI score 34 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. .lock's closest 2012 strings: .safe scored 38, 2 names; .locker scored 20, 9128 names; .secure scored 55, 2 names.101001K10K100K1M020406080100scored 60+: median 27Kunder 30: median 30.safe · 38 · 2.locker · 20 · 9K.secure · 55 · 2the AI’s blind 2012 score of each string (its own scale) →names held today (log) →

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

The 2012 read is a separate, time-locked score on its own scale, so .lock’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, .safe, held 2 names, June 2026. .locker held 9,128; .secure held 2. Chosen by AI from every string in the 2012 round, without being told what happened to any of them.

  1. .safestrong parallel2 names, June 2026live since 2015 · uncontested in 2012 · scored 38* in 2012 · Amazon EU S.à r.l.See .safe in Stats

    Same bet: a short, concrete everyday object-word that doubles as a security metaphor, so the primary identity goes to anyone selling protection rather than to one company or one industry.

  2. .lockerstrong parallel9,128 names, June 2026live since 2016 · uncontested in 2012 · scored 20* in 2012 · Dish DBS CorporationSee .locker in Stats

    Same bet from the same word family: a physical containment noun sold as a storage-and-security namespace, depending on buyers reading the object both literally (keep your things here) and figuratively (your data is secured).

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

    Same buyer and same security-category positioning, but the bet rests on an adjective/verb state rather than a concrete object, so it reads as a claim about a site instead of a thing a registrant owns.

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

locksmiths and smart-lock or access-control vendors, cybersecurity tools, and crypto projects offering token-locking or vesting features

What a .lock domain is

.lock 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 .lock domain extension real yet?

.lock 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 .lock domain?

You can’t yet. A .lock 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 .lock was .safe, delegated on 5 December 2015.

Is .lock a real TLD?

Not yet. .lock is not in the DNS root, so nothing resolves under it. It’s here because .lock is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.

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

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