AntiMalwareJuly 14, 2026🇷🇺Translated from Russian

Telegram Loses Global Short Links as t.me Domain Disabled Worldwide by .me Registry

On July 13, internet users around the world noticed that Telegram short links using the t.me format had stopped opening in web browsers. The problem was first highlighted by the Russian publication Kode Durova.

Despite the disruption, the messenger itself continues to operate normally. Both the desktop version and mobile applications remain fully accessible, and t.me links continue to work when opened inside the Telegram app. The only affected functionality is external access through regular web browsers.

Technical Cause of the Outage

According to preliminary data, the t.me domain was effectively excluded from the DNS system at the registry level of the .me top-level domain. This domain zone belongs to Montenegro, and its operator is the company doMEn, selected by the local authorities.

Why the registry decided to disable the domain remains unclear. Among the possible reasons are a legal dispute, a compliance check, requests from government agencies, or a violation of the domain zone’s registration rules. No official statements have been issued at the time of publication.

Registration Status

Importantly, the domain remains officially registered to Telegram until 2035. This means the registration period has not expired, and the situation cannot be explained by simple administrative oversight or failure to renew the domain.

The resulting outage has created an unusual situation: Telegram services continue to function, channels and chats work without interruption, yet the familiar short links opened from a browser lead nowhere.

Until the cause is clarified and the domain is restored in the global DNS, users are advised to open t.me links directly through the Telegram application or wait for the technical issue to be resolved.

Related articles

HabrPolicy & Regulation

Web Certificate Trust Chains and State Access Risks Explained Amid Russian Banking Sanctions

The article explains the hierarchical structure of web certificates used for site authentication and traffic encryption, starting from highly protected root certificates stored in air-gapped facilities with Shamir's secret sharing for key protection. Intermediate certificates extend the chain of trust down to leaf certificates deployed on websites. Russian banks have turned to certificates issued under the MinTsifry root after Western and Chinese CAs refused service due to sanctions. The piece highlights that any nation-state with access to a root private key, whether FSB, NSA, or others, could theoretically issue fraudulent certificates for any domain. It notes the limitations of the X.509 standard, which lacks native support for multi-CA signatures, and suggests that separate browsing environments or PGP-style web-of-trust models could mitigate risks. The author concludes that security is already reduced by reliance on any state-controlled CA and that the choice is ultimately which intelligence agency one prefers to trust.

AntiMalwarePolicy & Regulation

MAX Messenger to Open Source Code and Launch Developer Program for Alternative Clients

The Russian messenger MAX is preparing to open its platform to third-party developers by launching a dedicated developer program and providing API access. Approved participants will receive the official client's source code, design system, technical documentation, and access tokens to integrate with the platform infrastructure. The initiative targets IT companies from Russia and friendly countries that demonstrate experience with large-scale projects and adherence to strict security standards. All selected developers must implement secure development practices, robust encryption mechanisms, and undergo code audits to protect user data. The program supplies ready-made user registration and anti-fraud tools, while alternative clients remain bound by API usage terms focused on security compliance. Applications will be accepted via the official developer portal, although exact launch dates have not yet been disclosed.

HabrPolicy & Regulation

InfoWatch Details ARMA Wall NGFW Development for Industrial Systems Under Russian Import Substitution Rules

InfoWatch has published the second part of its interview series describing the ongoing development of the ARMA Wall next-generation firewall for industrial control systems. The product prioritizes on-premise processing without cloud agents to meet strict customer security policies and certification requirements. Engineers combine proprietary detection feeds with external sources, including indicators from NKCKI, while maintaining hundreds of thousands of signatures without disabling legacy rules for older Siemens controllers. Migration support relies on manual pre-project audits rather than automated tools, and the company works closely with domestic SCADA vendors to embed NGFW capabilities inside long-lifecycle OT environments. ARMA Wall is positioned as a more flexible and cost-effective alternative to data diodes because it allows granular command-level filtering and can emulate one-way traffic when required. The solution is already deployed at Roscosmos subsidiary RKK Energia after full certification and categorization.

AntiMalwarePolicy & Regulation

WhatsApp Developing AI Content Labeling Feature for Channel Admins to Meet EU Transparency Rules

WhatsApp, owned by Meta, is rolling out a new function that allows channel administrators to mark posts containing AI-generated or AI-edited media. The feature appears in the latest Android beta and stems directly from European Union requirements for transparency around artificial intelligence content. Administrators can long-press a message after publication and select an option to add an AI content label, which then displays a visible tag informing subscribers that the material was created or modified by neural network tools. The requirement applies specifically to images, videos, and other media files, while generated text remains exempt from mandatory labeling. WABetaInfo researchers spotted the change, noting that the label may become permanent once applied and that the rollout could initially target only jurisdictions with relevant legislation. Broader availability for iOS users and global deployment remain under consideration.