Telegram's t.me domain has been suspended

Original Article ↗ Hacker News Discussion ↗

Telegram’s short-link domain t.me was briefly suspended with a “serverHold” status by the .ME registry, knocking out image previews and integrations that depended on it. Commenters trace the action to OFAC-related sanctions compliance by the registry’s main corporate owners (GoDaddy and Identity Digital), rather than to the Montenegrin state itself, and note the domain has since been restored. The incident fuels broader concerns about relying on country-code TLD “hacks,” centralized DNS control, and large registrars whose business or political constraints can abruptly disrupt critical services.

What happened to t.me?

  • Some users saw t.me working; others saw it fail due to DNS changes not yet propagating.
  • Registry data showed serverHold status, which means the domain was removed from DNS and effectively suspended.
  • Later comments note that DNS delegation was restored and t.me came back online, with no official public explanation yet.

Technical details: domain status and interpretation

  • serverHold is set by the registry (for .me, doMEn), not the registrar (GoDaddy).
  • People link to ICANN docs explaining serverHold as “not activated in DNS” and often used around legal disputes.
  • Other status flags like serverDeleteProhibited and clientRenewProhibited are discussed; some note these can also be legal‑dispute related, others point out ccTLDs can interpret codes differently.
  • There’s debate about the “10‑year max renewal” rule; clarified that this is for gTLDs like .com, while ccTLDs can choose different policies.

Who suspended it and why?

  • One commenter reports a reply from Identity Digital (a major .ME operator) saying t.me was placed on serverHold due to “OFAC‑related compliance requirements,” and that further details must go via GoDaddy.
  • OFAC had reportedly sanctioned a VPN that used a t.me URL; some speculate this could have triggered over‑broad action against the domain.
  • Others initially blamed the Montenegrin government; later posts note .ME’s registry company is majority‑owned by US firms (GoDaddy and Identity Digital), raising questions about sovereignty vs. US compliance pressure.
  • Exact legal basis and decision process remain unclear.

Impact on users and mitigations

  • Developers relying on t.me for image or profile links saw breakage and began switching to telegram.me or other domains.
  • Some endorse using first‑party redirect URLs (on one’s own domain) to point to Telegram links, so only the redirect needs updating.

Registrars, TLD choice, and governance

  • Extensive debate over registrar choices: criticism of GoDaddy’s practices, support/concern for Namecheap, Cloudflare, Porkbun, Dynadot, Squarespace, etc.
  • Several argue critical services should avoid ccTLD “hacks” (.me, .io, etc.) because they’re geopolitically and procedurally less stable.
  • Others counter that all TLDs are ultimately subject to some state’s jurisdiction; global DNS centralization and US influence are recurring concerns.

Telegram, law enforcement, and content concerns

  • Discussion connects the suspension to ongoing legal/regulatory pressure on Telegram (Russia, France, India, and now US sanctions context).
  • Some claim Telegram resists court orders even when technically able to comply, leading authorities to seek leverage via infrastructure (domains).
  • Others argue that private communication should not be surveilled, and that platform liability for user behavior is being stretched.
  • There’s debate over Telegram’s role in extremism, drugs, and organized crime versus it being just another low‑censorship communication tool.