The editorial argues t.me is the primary user-facing surface of Telegram — every channel invite, bot deep link, share button, and QR code routes through it. While mobile apps still work via MTProto, the connective tissue between the open web and Telegram is severed, breaking hundreds of millions of indexed links across documentation, READMEs, job listings, and crypto projects.
By submitting the raw whois lookup showing the serverHold status flag, Tiberium framed this as a significant, verifiable event worth broad developer attention. The 302-point score and 220 comments within hours signal the community agreed this is a major infrastructure story, not a minor DNS blip.
The editorial argues that registry-level holds on domains of this scale are almost never accidents — they typically follow a legal order, a registrar dispute, an unpaid renewal that escalated, or a UDRP-style action. Because .me is Montenegro's ccTLD operated by doMEn d.o.o. under government contract, the action implicates state-level or contractual enforcement rather than a technical glitch.
A whois lookup on t.me now returns the status flag `serverHold` — the registry-level version of a suspension. When a domain is on serverHold, the registry has pulled it from the DNS zone. It doesn't resolve. It doesn't matter what nameservers the registrant has configured, what the SSL cert says, or whether the registrar dashboard still shows it as "active." The zone doesn't publish the record, so the domain effectively doesn't exist on the internet.
t.me is not a vanity domain for Telegram — it is the primary user-facing surface of the entire platform. Every public channel invite (`t.me/somechannel`), every bot deep link (`t.me/YourBot?start=payload`), every one-tap join flow, every share button embedded in a webpage, every QR code printed on a conference badge points at t.me. The primary telegram.org marketing site is unaffected, and the mobile apps themselves talk to Telegram's own MTProto servers directly, so existing chats keep flowing. But the connective tissue between the open web and the Telegram network — the thing that lets a tweet, a Discord message, or a landing page bounce a user into a channel — runs through the suspended domain.
The .me namespace is Montenegro's country-code TLD, operated by doMEn d.o.o. under contract with the Montenegrin government. Registry-level holds on a domain of this size are almost never accidents; they're almost always a response to a legal order, a registrar dispute, an unpaid renewal that escalated, or a UDRP-style action. Telegram has not, as of publication, issued a public statement clarifying which.
The Hacker News thread on the whois record climbed past 300 points inside a few hours, and the top comments are doing the math on blast radius. It's ugly. If you've ever pasted a t.me link into a documentation site, a README, a job listing, or a support macro, that link is dead until further notice. Search engines have indexed hundreds of millions of them. Every crypto project that ships "join our Telegram" as an onboarding step just lost its funnel. Every OSS maintainer running a support channel has an audience they can no longer route to. Every OAuth flow that whitelisted `t.me` in a redirect allowlist is now broken in a way that looks, from the user side, like the login button is haunted.
The deeper concern is that this exposes a category of dependency that most engineering orgs don't track. You audit your npm tree. You inventory your cloud vendors. You have a runbook for when AWS us-east-1 melts. Almost nobody has a runbook for "the third-party ccTLD hosting our community's canonical URL got put on serverHold by a registry in Podgorica." The failure mode isn't in your stack, isn't in your provider's stack, and isn't even in the platform you're integrating with — it's two hops away, at a sovereign registry you've probably never named in a design doc.
Compare this to the last few high-profile ccTLD incidents. The .io situation earlier this decade sparked panic when the British Indian Ocean Territory's political status shifted and everyone realized how many YC-era startups had bet their brand on a geopolitically contingent suffix. The .af, .ly, and .sy namespaces have all had moments where registry policy or state instability translated directly into broken production URLs. A ccTLD is a governance choice dressed up as a technical one, and every time you use one you're accepting a jurisdictional dependency you can't hedge with multi-region.
The community reaction on HN split predictably. One camp is treating this as a temporary registrar squabble that will be resolved in hours — Telegram is too big, too lawyered, and too politically connected in enough countries to stay dark for long. The other camp is pointing out that Pavel Durov's ongoing legal exposure in France, plus a long queue of takedown requests routed through .me over the years, makes a coordinated action more plausible than the usual "forgot to renew" story. Both readings are consistent with the evidence currently visible. The whois record alone doesn't tell you which.
If you ship anything that depends on t.me resolving, treat this as a P1 today. Concrete moves:
Audit your redirects. Grep your codebase, your CMS, your email templates, and your customer-facing docs for `t.me/`. Anywhere you find one, either swap it for `telegram.me` (the older backup domain, currently unaffected but sitting on the same registry, so hedge accordingly) or point it at an internal redirect service you control. The internal redirect gives you a single knob to turn the next time this happens.
Rotate your OAuth allowlists. If you use Telegram Login Widget, its callback flow assumes `oauth.telegram.org` and t.me subpaths. Validate what your identity provider actually has whitelisted and add fallbacks. Same for any deep-link handling in mobile apps that string-matches on the t.me host — an unhandled scheme is a silent conversion killer.
Stop treating ccTLDs as free brand real estate. If a URL is load-bearing for your product, the TLD choice is an architectural decision, not a marketing one. Bit.ly, t.co, youtu.be, discord.gg, git.io — every short URL you touch is a ccTLD wrapped in a corporate wrapper, and every one of them has the same failure mode as t.me does right now. The cost of migrating off a short domain scales with how many external links you've minted, which is exactly why it never gets prioritized until an incident like this one.
Odds are t.me comes back online within days — a registrar-level dispute this loud gets resolved once lawyers are in the room, and Montenegro's registry has commercial incentives not to be seen as the operator that unilaterally broke a platform with a billion users. But the useful lesson isn't whether it comes back; it's that the risk was always there and almost nobody's incident playbook had a page for it. The next post-mortem you write on a third-party outage is a good excuse to add one.
Of course we launched our Telegram channel just this weekend, so I am feeling pretty happy that I enforced a 15-year old SOP that says "never email links to 3rd-party domains ; always use a redirect"...Swapping the redirect now for telegram.me, which hopefully won't go down simultaneo
I can't believe they use GoDaddy as a registrar.
You can read an explanation of the status codes on the icann website.The explanation for clientRenewProhibited was interesting:"This status code tells your domain's registry to reject requests to renew your domain. It is an uncommon status that is usually enacted during legal disputes or w
Telegram is currently the target of legal/regulatory investigations by Russia (alleged extremism), France (likewise), and India (alleged facilitation of national exam leaking/cheating). I'm guessing the latter since it's the most recent and arguably has the most fiscal heft.Also
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
I found this post: "I contacted Identity Digital, the registry operator for the .ME domain zone, to request the reason why t.me was placed on "serverHold".The company has now responded and confirmed that the domain was suspended due to OFAC-related compliance requirements.The domain t