The domain t.me, which Telegram uses for its short-link service, is no longer resolving after its registrar, GoDaddy, applied a serverHold status. The change was recorded in the public WHOIS database on 13 July 2026, and the domain’s DNS nameservers remain configured but are now unreachable by resolvers worldwide.
Background: The .me top-level domain (TLD) is operated by the Montenegrin government and managed by Identity Digital (formerly Afilias). A serverHold status is an ICANN-defined state that removes a domain from the DNS root zone, effectively taking it offline without deleting the registration. Registrars typically apply this status in response to legal orders, abuse complaints, or unpaid fees.
What happened
On 13 July 2026, the WHOIS record for t.me was updated to include the serverHold status. This status prevents the domain from resolving, even though the registration itself remains active and is set to expire in 2035. The domain’s nameservers—four Google Cloud DNS endpoints—are still listed in the WHOIS record, but queries to those servers now fail to return any records for t.me.
Telegram has not issued a public statement about the suspension. GoDaddy, the sponsoring registrar, has not commented on the reason for the status change. Identity Digital, the registry operator for .me, also has not provided an explanation. The lack of transparency leaves the cause of the suspension unclear, though industry observers note that serverHold is commonly used to enforce court orders or regulatory demands.
Why it matters
The t.me domain is a critical infrastructure component for Telegram, which uses it to generate short links for channels, groups, and bots. These links are widely shared across social media, messaging apps, and websites, meaning the suspension disrupts access to millions of public Telegram resources. While the main Telegram app and website (telegram.org) remain operational, any user attempting to visit a t.me link is met with a DNS resolution error.
For hosting and DNS providers, the incident highlights the risks of relying on a single domain for high-traffic services. The suspension also raises questions about the due process and transparency surrounding domain suspensions, particularly for domains associated with widely used platforms. Without public disclosure from the involved parties, speculation about the cause—whether legal, technical, or financial—remains unconfirmed.
What to watch
The duration of the suspension will depend on whether Telegram, GoDaddy, or Identity Digital resolve the underlying issue. If the suspension is due to a legal dispute, the timeline could extend for weeks or months, depending on the jurisdiction and nature of the complaint. Industry professionals will be monitoring for any official statements from Telegram or the registrar, as well as changes in the domain’s WHOIS status.
In the meantime, users and developers who rely on t.me links may need to implement workarounds, such as redirecting traffic through Telegram’s primary domain or caching link destinations locally. The incident also serves as a reminder for platforms to diversify their domain strategies to mitigate the impact of potential suspensions or outages.
Companies mentioned
Automated pipeline · Domains
Synthesized from 1 industry feed on 13 Jul 2026. Passed independent editor verification (score 92/100) before publication. Style guide v1.4.
Sources
Decision trail
- Checking for duplicates — Deduped batch of 1 candidates
- Checking for duplicates — New story No previously published or in-pipeline article covers this story.
- Checking for duplicates — New story pre_write:; No previously published or in-pipeline article covers this story.
- Writing the article — Draft created article_id=318 slug=telegram-s-t-me-domain-placed-on-serverhold-by-registrar
-
Editor review — Approved
- Score: 92/100
- Factual grounding: The draft states the WHOIS record was updated on '13 July 2026', which matches the 'Updated Date' in Source 1 (2026-07-13T19:24:55Z). However, the source does not explicitly state the event (serverHold application) occurred on that date—only that the record was updated. The timing is plausible but not explicitly confirmed as the event date.
- Style compliance: The standfirst ('The t.me domain, used for Telegram’s short links, has been suspended at the registry level.') is slightly misleading. The domain is suspended at the registrar level (GoDaddy applied serverHold), not the registry level (Identity Digital). The registry merely reflects the status.
- Audience relevance and notability: The draft does not explicitly address whether Telegram is an industry-notable entity for Hostingpaper's audience. While Telegram is widely known, the article should clarify its relevance to hosting/DNS/email professionals (e.g., reliance on t.me for infrastructure, DNS resolution failures). This is implied but could be more explicit.
- Generating reader Q&A — Generated 4 items
- Assigning hero image — Rejected library image #140: The candidate depicts GoDaddy's headquarters, which is unrelated to the article's focus on Telegram's t.me domain being placed on serverHold. The alt text and context do not match the DNS or domain suspension topic.
- Assigning hero image — Reused library image pexels_id=17489158 q=domain status serverHold error screen picker=The candidate (index 35) shows a close-up of a blue screen error on a data center control terminal, which directly illus
- Linking related stories — Linked 0 relations from 264 candidates
- Publishing — Published telegram-s-t-me-domain-placed-on-serverhold-by-registrar
- Mastodon — Posted https://mstdn.social/@hostingpaper/116915121767373052

Discussion · coming soon
Be the first to join the thread when community discussion launches.