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

.engine

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

.engine is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Identity Digital. XYZ Registry named .engine as a backup string for its .kit application. ICANN’s list shows it as deactivated: the application cannot move to it. Intercap named .engine as a backup string for its .robot application. ICANN’s list shows it as deactivated: the application cannot move to it.

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

Who is applying, and what they run today

Identity Digital filed 216 applications across the round.

  • Agador Slip, LLC

    Identity Digital

    controlled by Ethos Capital Digital Infrastructure UGP LLC

    277 TLDs · 14.80M names: .info 5.63M, .pro 1.25M, .live 672K, .parts 8K (2012 comp), .systems 45K (2012 comp)

    backup .esports, 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
  • IntercapDeactivated backupintercap.inc ↗

    Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .robot application, shown as deactivated: another applicant applied for the same string or named it as a backup

    Deactivated backup for .robotGenericICANN IRI2679T-T49225ICANN ↗
  • XYZ RegistryDeactivated backupxyz.xyz ↗

    Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .kit application, shown as deactivated: another applicant applied for the same string or named it as a backup

    Deactivated backup for .kitGenericICANN XL2625T-T72611ICANN ↗

Will names sell?

◈AI score
42/ 100
Usable but limited

A clean tech word that fits product names like search.engine, but most serious projects will still default to .com or .ai.

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. .engine’s closest 2012 strings hold .cloud 552K, .systems 45K and .parts 8K.

AI score 42 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. .engine's closest 2012 strings: .cloud scored 70, 551867 names; .systems scored 40, 44956 names; .parts scored 40, 8017 names.101001K10K100K1M020406080100scored 60+: median 27Kunder 30: median 30.cloud · 70 · 552K.systems · 40 · 45K.parts · 40 · 8Kthe AI’s blind 2012 score of each string (its own scale) →names held today (log) →

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

The 2012 read is a separate, time-locked score on its own scale, so .engine’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, .cloud, held 551,867 names, June 2026. .systems held 44,956; .parts held 8,017. Chosen by AI from every string in the 2012 round, without being told what happened to any of them.

  1. .cloudstrong parallel551,867 names, June 2026live since 2015 · 7 applications in 2012 · scored 70* in 2012 · ARUBA S.p.A.See .cloud in Stats

    Same bet: an unowned singular common noun for a piece of technical infrastructure that works mainly as a metaphor, sold to software builders who want their platform's core capability to be their identity, and which pays off only if the metaphor stays fashionable.

  2. .systemsmoderate44,956 names, June 2026live since 2013 · uncontested in 2012 · scored 40* in 2012 · Dash Cypress, LLCSee .systems in Stats

    Same bet on the generic engineering-capability noun that B2B firms bolt onto their own name as a competence claim ('Acme Systems' / 'Acme Engine'), with no defined community and no incumbent registrant pool to anchor demand.

  3. .partsmoderate8,017 names, June 2026live since 2014 · uncontested in 2012 · scored 40* in 2012 · Sea Goodbye, LLCSee .parts in Stats

    Covers the literal reading of the target: a plain component noun whose buyers are automotive and industrial aftermarket sellers, where the string's value is search-matched commerce intent rather than brand metaphor.

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

software and AI product teams naming an "X Engine" (search, game, rendering, inference, pricing engines), plus a secondary automotive and motorsport crowd

What a .engine domain is

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

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

You can’t yet. A .engine 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 .engine was .cloud, delegated on 26 June 2015.

Is .engine a real TLD?

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

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

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