.find

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

.find is contested: 3 applications for it are on ICANN’s Reveal Day list, as of 8 October 2026. They are Google Registry, Intercap and Link Freedom Group. Identity Digital named .find as a backup string for four of its applications: .race, .pot, .mcp and .check. ICANN deactivated those backups, because another applicant applied for the same string or named it as a backup. GoDaddy Registry named .find as a backup string for its .list application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup. ShortDot named .find as a backup string for its .why application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.

Generic applications · AI & tech · on the record since Aug 15, 2026, updated Oct 8, 2026
applicants
3 applications · 6 deactivated backups

Who is applying, and what they run today

Two of the three already run TLDs, 2.34M names between them. One runs one of .find's closest 2012 strings: Google Registry .search. Link Freedom Group runs none.

  • Charleston Road Registry Inc.

    Google Registry

    controlled by Alphabet Inc.

    46 TLDs · 2.33M names: .app 1.48M, .dev 713K, .page 41K, .search 1 (2012 comp)

  • Intercap Registry Inc.

    Intercap

    controlled by Jason Adam Chapnik

    4 TLDs · 11K names: .inc 8K, .box 3K, .dealer 222

    backup .look, disallowed

  • Link Freedom Group Ltd

    Link Freedom Group

    controlled by Vandelay Investments Ltd, Yonatan Belousov

    runs no TLD today

    backup .human, 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.

backups
  • ShortDotDeactivated backupshortdot.bond ↗

    One of the 80 strings ShortDot published for the ICANN 2026 round. ShortDot states it has submitted 40 applications, but publishes the 80 strings without revealing which 40 are applications and which 40 are designated replacements. The submission claim is therefore applicant-level, not string-level: nothing in the source says ShortDot applied for THIS string. Catalogued, not announced.

    listed in a catalog Sep 8, 2026 · announced Sep 9, 2026 · abandoned Oct 7, 2026 · named as a backup for .why, deactivated by ICANN Oct 7, 2026

    Deactivated backup for .whyGenericICANN NA2626T-T95997ShortDot (Ireland) Limited ↗
  • Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .list application, shown as deactivated: another applicant applied for the same string or named it as a backup

    Deactivated backup for .listGenericICANN NA2631T-T12521ICANN ↗
  • Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .check application, shown as deactivated: another applicant applied for the same string or named it as a backup

    Deactivated backup for .checkGenericICANN TCL2632T-T19690ICANN ↗
  • Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .mcp application, shown as deactivated: another applicant applied for the same string or named it as a backup

    Deactivated backup for .mcpGenericICANN TCL2632T-T27609ICANN ↗
  • Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .pot application, shown as deactivated: another applicant applied for the same string or named it as a backup

    Deactivated backup for .potGenericICANN TCL2632T-T51366ICANN ↗
  • Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .race application, shown as deactivated: another applicant applied for the same string or named it as a backup

    Deactivated backup for .raceGenericICANN TCL2632T-T67204ICANN ↗

Will names sell?

◈AI score
38/ 100
Usable but limited

A pleasant generic verb for search and discovery tools, but most serious projects would still put their main identity elsewhere.

assessed by claude-fable-5 · Aug 15, 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. .find’s closest 2012 strings hold .search 1, .seek 11 and .compare 964.

AI score 38 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. .find's closest 2012 strings: .search scored 55, 1 names; .seek scored 20, 11 names; .compare scored 32, 964 names.101001K10K100K1M020406080100scored 60+: median 27Kunder 30: median 30.search · 55 · 1.seek · 20 · 11.compare · 32 · 964the AI’s blind 2012 score of each string (its own scale) →names held today (log) →

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

The 2012 read is a separate, time-locked score on its own scale, so .find’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, .search, held 1 names, June 2026. .seek held 11; .compare held 964. Chosen by AI from every string in the 2012 round, without being told what happened to any of them.

  1. .searchstrong parallel1 names, June 2026live since 2017 · 4 applications in 2012 · scored 55* in 2012 · Charleston Road Registry Inc.See .search in Stats

    The same bet exactly: a bare generic verb for the act of locating something, owning no category of its own, aimed at whoever wants to claim the discovery function itself rather than a subject matter.

  2. .seekstrong parallel11 names, June 2026live since 2015 · uncontested in 2012 · scored 20* in 2012 · Seek LimitedSee .seek in Stats

    Another single-syllable looking-for verb resting on the same premise as .find — that a namespace named after the user's action, not the thing acted on, can carry a discovery or classifieds operator's primary identity.

  3. .comparemoderate964 names, June 2026live since 2016 · uncontested in 2012 · scored 32* in 2012 · iSelect LtdSee .compare in Stats

    Same structural bet of a generic transactional verb sold as a utility layer, but narrower because it presupposes a purchase-decision use case where .find stays open to any kind of lookup.

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.

Where they meet elsewhere

Identity Digital and Link Freedom Group face each other in 68 contests this round, .find included.

  • Identity Digital × Link Freedom Group
    68
  • Identity Digital × GoDaddy Registry
    51
  • Identity Digital × Intercap
    34
  • Link Freedom Group × GoDaddy Registry
    32
  • Link Freedom Group × Intercap
    31

Shared contests: strings where both companies hold an application on ICANN’s list. Companies that meet another here in fewer than three are left out.

who it’s for

builders of search, discovery, directory, marketplace and recommendation products who want a verb-styled name (jobs.find, homes.find), plus SEO-minded lead-gen sites and name-hack enthusiasts

What a .find domain is

.find is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our AI & tech category. 3 applications for it are on ICANN’s Reveal Day list.

Is the .find domain extension real yet?

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

You can’t yet. A .find 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 .find was .search, delegated on 29 June 2017.

Is .find a real TLD?

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

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

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