Telegram short links in the .me domain zone have stopped opening in browsers around the world due to the actions of the .me domain registry. This is evidenced by data from web resource tracking services.
Telegram short links in the .me domain zone have stopped opening in browsers around the world due to the actions of the .me domain registry. This is evidenced by data from web resource tracking services.
The t.me domain received the serverHold status in the WHOIS record — this means that the .me domain zone registry has removed the domain’s delegation in the global DNS system.
The serverHold status is imposed at the level of the domain registry itself, not the registrar, and, according to ICANN’s description, completely excludes the domain from the name resolution system — no matter how correctly the service infrastructure is configured, the browser simply cannot associate the t.me address with the server.
The number of complaints about malfunctions is increasing.
The Telegram application — both mobile and desktop — continues to work as usual: it does not depend on the browser recognizing the t.me domain. The failure affects the transition via short links, not the messenger itself.
The problem was first reported by X users. The International Cyber Digest account wrote that the .me registry implemented serverHold without any public explanation — neither from Telegram, nor from the registry itself, nor from the operator Identity Digital; a similar assessment was made by the Dark Web Informer account.
The Zatravast account claims that the telegram.org domain, which is involved in the service’s infrastructure, has also been removed from delegation, and this allegedly explains why some users still do not open links — due to the local DNS cache not yet being updated.
User Pedro Havay noted that the .me zone registry imposed the block, removing t.me from the global DNS and thereby simultaneously «breaking» all links to the domain.
The fact that telegram.me — also a domain in the .me zone — was not affected clarifies the nature of the restriction: it appears to apply specifically to the t.me domain, and not to the entire .me domain zone in general.
Neither Telegram nor the .me domain zone registry have yet provided official comments on the reasons for the restriction.
