.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 named .engine as a backup string for its .kit application. ICANN deactivated it, because another applicant applied for the same string. Intercap named .engine as a backup string for its .robot application. ICANN deactivated it, because another applicant applied for the same string.
A clean tech word that fits product names like search.engine, but most serious projects will still default to .com or .ai.
software and AI product teams naming an "X Engine" (search, game, rendering, inference, pricing engines), plus a secondary automotive and motorsport crowd
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
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
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.
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.
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.
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.
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, filed under AI & tech. 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. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .engine name can only be registered after that, once the string is delegated 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.
“ASL2693T-T32133 · Agador Slip, LLC · primary IRI2679T-T49225 · Intercap Registry Inc. · replacement string of .robot · Deactivated XL2625T-T72611 · XYZ.COM LLC · replacement string of .kit · Deactivated”ICANN
- Band chosen: 30-49 (usable but limited). "Engine" is a strong, ubiquitous product-naming noun in software: search engines, game engines, rendering engines, inference and recommendation engines, pricing engines. That gives the string a natural suffix structure (word.engine) that reads as a product name rather than a web address, which is the same dynamic that helped .app and .dev find primary-identity use; by analogy, that pattern is the string's main asset. It also has a real secondary meaning in automotive and motorsport, which broadens registration demand but muddies the brand signal. It is not in the 50-69 band because, by analogy with single-noun tech TLDs such as .systems, .tools, .network and .solutions, demand for this kind of string has tended to be defensive or price-driven, with few serious projects adopting the TLD as their primary identity over .com or .ai, and with a thin aftermarket; a project called "Vector Engine" is more likely to live at vectorengine.com or vector.ai than at vector.engine. It is not in the 10-29 band because the word is neither a joke nor event-driven: it is a durable category term in software and AI that should produce sustained, if modest, registrations over the next 5 years, and a handful of credible product sites using it as their home address is plausible. The record shows one confirmed application, from Agador Slip, LLC, on the ICANN Reveal Day list of 7 October 2026, with no category tag recorded; a single uncontested applicant says nothing about the string's market and is noted only as context. Main market uncertainty: whether the "X Engine" naming convention in AI and developer tooling converts into primary-identity domain use on this TLD, or stays a .com/.ai habit with .engine held only as a redirect. Registry pricing and launch positioning are unknown.