Telegram’s t.me Domain Suspended, Breaking Links Worldwide

Key Takeaways

• Telegram’s primary short-link domain, t.me, has been placed on “serverHold” by the .me registry.
• This registry-level action has disabled the domain globally, rendering all t.me short links non-functional.
• The core Telegram messaging application remains operational, with the disruption isolated to link resolution.
• The cause of the suspension is currently unknown, with no official statements from Telegram or the .me registry.

The core t.me domain, vital for Telegram’s short links and web previews, has been suspended at the registry level, causing widespread disruption to link functionality across the internet. The domain now carries a “serverHold” status, a critical flag that effectively removes it from the global Domain Name System (DNS).

Registry-Level Suspension Confirmed

WHOIS records corroborate the domain’s altered status, displaying eight flags, including “serverHold,” “clientDeleteProhibited,” and “serverDeleteProhibited.” The timestamp for these changes is recorded as 2026-07-13T19:24:55Z. Despite this, the domain remains registered with GoDaddy.com, LLC, indicating its registration is active until May 20, 2035, and ruling out non-renewal as the cause of the suspension. The domain’s name servers continue to point to Google’s cloud infrastructure (ns-cloud-b1 through b4.googledomains.com), suggesting that the DNS delegation itself is intact, but the .me registry has imposed an override at a higher hierarchical level.

The “serverHold” status is an EPP (Extensible Provisioning Protocol) code that only the domain’s registry, in this instance the .me registry operated by Identity Digital, can apply. This status takes precedence over any settings configured by the registrar or DNS provider. When activated, it effectively disables the domain’s entire DNS zone, preventing the associated website, email services, and any dependent services from resolving anywhere on the internet. This differs significantly from a “clientHold,” which registrars might apply for issues such as unverified contact information; “serverHold” is reserved for more severe registry-level actions, including fraud investigations, security concerns, legal disputes, or abuse flags.

Unconfirmed Cause and Isolated Impact

As of this report, neither Telegram, the .me registry, nor its backend operator, Identity Digital, has released an official statement clarifying the reason behind the suspension. The absence of “clientHold” or transfer-related status codes suggests the action originated from the registry rather than Telegram’s registrar account. However, the precise trigger—whether a security incident, a compliance dispute, or an administrative oversight—remains unconfirmed.

Independent outage trackers have not reported any application-level disruptions to Telegram’s core messaging service. This indicates that the impact is currently confined to the t.me short-link and web-preview domain, rather than Telegram’s primary operational infrastructure. Until the registry lifts the hold, all links relying on the t.me domain—including invite links, channel previews, and shared message URLs—will fail to resolve globally, even as the Telegram application itself continues to function via its primary domains and IP-based connections.

Restoring a domain from “serverHold” status typically requires the registrant or registrar to address the underlying concern with the registry. Industry precedent suggests this process can take anywhere from a few hours to several days, depending on the complexity and nature of the issue that prompted the suspension.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.