Telegram's t.me domain has been suspended
Telegram's widely used 't.me' short domain was unexpectedly placed on a 'serverHold' by the .ME registry, causing immediate service disruptions for some users. This revelation sparked a discussion on HN about the technicalities of domain suspensions, the reliability of centralized DNS, and criticisms of registrars like GoDaddy. The incident highlights the fragility of internet infrastructure and the power wielded by domain registries.
The Lowdown
The Hacker News community buzzed over the sudden suspension of Telegram's 't.me' domain, a critical short-link used across its platform. A WHOIS lookup revealed the domain was under a "serverHold" status, indicating a suspension imposed by the .ME registry itself, not its registrar, GoDaddy. This technical detail sparked immediate concern and confusion among users about the reasons behind such a significant action.
- The 't.me' domain's WHOIS record displayed a "serverHold" status, which signifies a domain suspension by the registry.
- This suspension was not due to expiration, as the domain is registered until 2035.
- Early reports from users confirmed service impact, with some noticing broken links and images in Telegram mini-apps.
- Initial confusion arose from differing DNS propagation times, leading some to believe the domain was still functional.
- The original poster clarified that the .ME registry, not GoDaddy, initiated the "serverHold" status, distinguishing it from a "clientHold."
While no official explanation for the suspension was provided, the incident underscored the potential for single points of failure in internet infrastructure and prompted users to consider alternatives to centralized domain systems.
The Gossip
Domain Debacle Details
The primary discussion revolved around understanding what "suspended" meant in this context. Users initially questioned if the domain was truly down, experiencing inconsistent access due to DNS propagation delays. The original poster clarified that the "serverHold" status, set by the .ME registry, unequivocally means suspension, distinguishing it from registrar-imposed "clientHold." The lack of official explanation for the suspension fueled speculation about potential legal issues.
Registrar Rants & Recommendations
A significant portion of the comments veered into criticizing GoDaddy, the domain's registrar, despite the clarification that the .ME registry was responsible for the "serverHold." Users expressed general distrust and aversion to GoDaddy, often citing past experiences or perceived poor practices. This also led to recommendations for alternative registrars, with Namecheap being mentioned as a popular choice, though some admitted they hadn't encountered issues with GoDaddy personally.
Centralization Concerns & Crypto Critiques
The incident prompted a broader philosophical discussion about the centralized nature of DNS and internet infrastructure. Some commenters expressed concern over the power wielded by registries and registrars, fearing that "they" could easily disrupt services. This led to suggestions for decentralized alternatives, specifically mentioning blockchain-based domain systems like Handshake (HNS) as a potential solution to mitigate such single points of failure.