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
MinTsifry Proposes Requiring Telecom Operators to Install SORM Equipment Before Obtaining Licenses
The Russian Ministry of Digital Development plans to introduce legislation obligating telecom operators to deploy SORM surveillance systems prior to receiving operating licenses. Under the proposed rules, companies will only be permitted to begin serving subscribers after the equipment has been installed and handed over to law enforcement agencies. Non-compliance could result in license revocation through an extrajudicial administrative process. Current regulations allow operators to obtain licenses with a network diagram that merely indicates planned or existing SORM components. The change aims to close loopholes exploited by unscrupulous providers that repeatedly register new legal entities to operate without surveillance capabilities. Industry experts note that the minimum cost of a basic SORM complex starts at 5 million rubles, which could disproportionately affect smaller local providers without a transition period or scaled requirements.
GOST R 57580 Compliance: Defining Assessment Scope to Verify Real Protection in Financial Organizations
Financial institutions often maintain extensive documentation on information security yet still fail GOST R 57580 assessments due to mismatches between documented processes and actual infrastructure. The standards GOST R 57580.1-2017 and GOST R 57580.2-2018 set distinct requirements for protection levels and evaluation methodology. Correct application begins with identifying the organization's regulatory category under Bank of Russia rules such as Regulation 851-P for credit institutions or Regulation 757-P for non-credit financial organizations. Defining the precise assessment boundary is critical, including systems, remote access channels, virtualization components, and third-party interactions. Organizations must also distinguish between the full assessment scope and the representative sample selected for verification. Evidence collection requires both policy review and technical confirmation that controls function as intended across the evaluated environment.
Evaluating Secure Development Maturity: Comparing BSIMM, DSOMM, SAMM and GOST R 56939-2024
A detailed analysis compares four methodologies for self-assessing secure software development maturity in Russian companies. The review covers BSIMM from Black Duck, OWASP DSOMM, OWASP SAMM and the updated Russian national standard GOST R 56939-2024. Each model was tested through a simulated audit on a fictional company called ООО «Лиса и лосЬ» that uses GitLab, Nexus and SonarQube. The evaluation scored the methodologies on criteria including ease of maturity calculation, recommendation generation, roadmap building, heat-map creation and SDLC coverage. GOST R 56939-2024 and SAMM received the highest total scores of 35 and 34 out of 47. The article concludes that no single methodology covers all needs and recommends combining approaches tailored to specific company contexts.
GlobalSign Launches New Wave of SSL/TLS Certificate Revocations Targeting Russian Organizations
GlobalSign has initiated another round of revocations affecting SSL/TLS certificates issued to Russian websites, with a total of 11,000 certificates withdrawn from 1,300 organizations so far. The revocations primarily impact entities listed in EU and US sanctions regimes, in line with updated CA/Browser Forum requirements that took effect in May 2026. Greek CA HARICA has also participated in the revocations, sometimes completing the process within seconds and leaving site owners little time to respond. The actions stem from mandatory checks against the OFAC SDN List, BIS Denied Persons List, and equivalent European sanctions databases. Russian authorities recommend obtaining domestic TLS certificates via Gosuslugi within three business days to maintain secure access in foreign browsers. Let's Encrypt has similarly updated its policies to restrict certificates for sanctioned Russian entities while continuing issuance for others.