.twt
Is .twt a real TLD? Who’s applying to run it?
Nobody has applied for .twt in its own right, as of 7 October 2026. Juming named .twt as the replacement string of its .mind application.
A three-letter string with no clear meaning; a few shorthand or novelty uses, not a serious primary identity for most.
registrants who want a short, abbreviation-style suffix — social-media shorthand ("tweet"-adjacent handles), initials, or novelty hacks — rather than a category-defined community
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: own the clipped, insider-typed form of a name rather than the formal word, so the string only means anything to people already fluent in the shorthand.
Same bet structurally: a vowel-dropped consonant skeleton of a platform's name that reads as gibberish to outsiders and is instantly expanded by the one community that uses the service.
Same bet of putting primary identity on the abbreviation people actually say instead of the full name, betting the short form carries more recognition than the thing it compresses.
What a .twt domain is
.twt is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Culture. Nobody has applied for .twt in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .twt domain extension real yet?
.twt 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 .twt domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .twt name can only be registered after that, once the string is delegated and its registry opens.
Is .twt a real TLD?
Not yet. .twt is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .twt as part of an application for another string. Every entry on this page links to its source.
- Juming · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The string .twt carries no dictionary meaning and no widely shared expansion; the most likely reading is as internet shorthand for a tweet or for a set of initials, which gives it memorability for a thin slice of personal and social registrants but no category whose members would adopt it as a default. It is not in the 30-49 band because volume registrations on meaning-neutral strings have historically depended on sustained price promotion and distribution rather than on the string itself, and, by analogy to other abstract three-letter new gTLDs, such volume rarely converted into primary-identity use or an aftermarket; nothing on the record suggests a plan of that kind, and the verified facts show it was filed as a replacement string for .mind rather than as a primary bet, which by analogy suggests limited dedicated marketing. It is not in the 1-9 band because short, pronounceable three-letter strings do attract some registrations as hacks and handles, and shorthand for tweeting is recognisable enough to produce event-driven or novelty demand within the next 5 years. Applicant facts (Juming / TechEdge Limited, standard application, replacement string of .mind, contention count 0) are stated neutrally and only bear on adoption likelihood. Main market uncertainty: whether any community actually reads 'twt' as a shared abbreviation (social-media shorthand, an organisation's initials, or a regional meaning) strongly enough to make it a chosen identity rather than a curiosity; the social-platform association is also weakened by that platform's rebranding, which is an inference from general knowledge, not a figure. Analogies to abstract-string gTLDs are flagged as analogy throughout.