.translate
Is .translate a real TLD? Who’s applying to run it?
Nobody has applied for .translate in its own right, as of 7 October 2026. .Prompt Inc. named .translate as the replacement string of its .prompt application.
A clear word for a real industry, but translation tools and agencies have little reason to move off their existing names.
translation and localization agencies, freelance translators, and makers of AI translation tools who want a descriptive address or a verb-style domain hack
No applications recorded for this TLD yet.
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 almost exactly: a generic word for the language-services trade itself, sold to the same fragmented population of agencies and freelancers who would put their primary identity on the category word rather than a brand.
Same bet shape one vertical over: a single narrow service category whose buyers are thousands of small independent providers, so it only works if that trade adopts the category word as its address instead of .com.
Another named single-service profession string betting that practitioners of one specific skilled service will self-identify under their own occupation word, with the same ceiling of a small, non-corporate registrant pool.
What a .translate domain is
.translate is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. Nobody has applied for .translate in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .translate domain extension real yet?
.translate 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 .translate domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .translate name can only be registered after that, once the string is delegated and its registry opens.
Is .translate a real TLD?
Not yet. .translate is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .translate as part of an application for another string. Every entry on this page links to its source.
- .Prompt Inc. · first recordedICANN
“PI2677T-T54890 · .Prompt Inc. · replacement string of .prompt”ICANN
- Band chosen: 30-49, usable but limited. The string is an unambiguous English verb naming a real commercial activity: translation and localization services, freelance translators, and the fast-growing field of machine and AI translation. That gives it a defined buyer group and some natural domain-hack appeal (a short word before the dot reads as a sentence). By analogy with other verb and service-word TLDs from the 2012 round (such as .help, .build, .review, .services — analogy, not data), such strings tend to see registrations driven by price and defensive or descriptive use rather than by projects choosing them as a primary brand; the aftermarket for them has generally been thin. It is not in the 50-69 band because the translation industry already has entrenched identities on legacy TLDs, and the most visible translation products are features inside larger platforms rather than standalone brands that would adopt a new namespace; a serious localization company picking a .translate address would still need to explain the choice. It is not in the 10-29 band because, unlike a joke or event string, the word maps onto an ongoing commercial category with sustained demand for descriptive names, and a verb TLD supports genuine primary-identity use for small services and tools. The applicant on record, .Prompt Inc., filed it as a standard application and as a replacement string for .prompt (verified facts); no other applicant is recorded, so there is no contention on record. Main market uncertainty: whether AI translation produces many standalone tools and services that want a category-specific address, or whether translation keeps collapsing into a built-in feature of larger platforms, which would leave this TLD with price-driven descriptive registrations only.