.telegram
Is .telegram a real TLD? Who’s applying to run it?
Nobody has applied for .telegram in its own right, as of 7 October 2026. Telegram named .telegram as the replacement string of its .gram application.
Only useful inside the Telegram world; a platform-tied address, not an identity a business would choose on its own.
telegram channel owners, bot and mini-app builders, and communities who want a web address that reads as their Telegram identity
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 exactly: a standalone consumer messaging/calling app whose product name IS the company's whole identity, applying to put a global user base of individual accounts behind a namespace it alone controls.
Also a mass-adoption consumer social-messaging platform claiming its own coined service name, though it leans on a parent company's portfolio and a single-market user base rather than a borderless independent app.
A messaging-product name taken as a string, but the bet is weaker because the applicant is a conglomerate protecting one feature brand among many, not a company whose entire identity rests on that word.
What a .telegram domain is
.telegram is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. Nobody has applied for .telegram in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .telegram domain extension real yet?
.telegram 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 .telegram domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .telegram name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .telegram was .skype, delegated on 23 June 2015.
Is .telegram a real TLD?
Not yet. .telegram is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .telegram as part of an application for another string. Every entry on this page links to its source.
- Telegram · first recordedICANN
“TF2633T-T82296 · Telegram FZ-LLC · replacement string of .gram”ICANN
- Band chosen: 30-49 (usable but limited). The string is a dictionary word (a telegraph message) but in current use it reads almost entirely as the name of one messaging platform, so a name on it carries meaning only in relation to that platform. The verified facts show it was applied for by Telegram FZ-LLC as a standard (open, non-brand) application and as the replacement string for a primary .gram application, which suggests the operator's first choice is the shorter string and this one is a fallback. Assuming it is delegated and generally available, the plausible shape is a namespace tied to the platform's channels, bots and user identities, in the way platform operators have run open TLDs such as .app and .dev — but by analogy those succeeded because the words were generic to a whole category, whereas .telegram names one product, which is why the TLD does not reach the 50-69 band: a serious project outside that ecosystem has no reason to make it a primary identity, and even inside it the platform already gives channels short share links, so the TLD has to earn a role rather than fill an obvious gap. It is above the 10-29 band because the platform has a very large active user base (scale unknown from the facts, stated qualitatively), a dense market of channels, bots and crypto/TON-adjacent projects that already treat their Telegram handle as a core identity, and an operator with the distribution to make the TLD visible by default — that is sustained, not event-driven, demand. Aftermarket is likely thin and probably operator-shaped: if names are bound to platform usernames (unknown), resale happens inside the platform rather than on domain marketplaces. Main market uncertainty: whether the operator runs it as a broad open namespace linked to platform identities, or as a lightly used reserved space while .gram carries the real product.