Why Legitimate Russian Websites Fail to Load With or Without VPN: TSPU RKN Blocking and MinTsifry Certificates Explained
Russian users continue to encounter difficulties opening legitimate domestic websites both with VPN enabled and when connecting directly. The root causes involve TSPU (Technical Means of Countering Threats) devices mandated for every ISP, Roskomnadzor filtering policies, and the shift to national MinTsifry certificates that foreign browsers reject.
TSPU units inspect all traffic passing through Russian providers. Their primary function is to locate and block prohibited content while also restricting certain foreign VPN services. Because these devices sit in the path of every connection, they can interfere with otherwise legal traffic under specific conditions.
Scenario 1: ERR_CONNECTION_TIMED_OUT when using VPN
When a VPN is active and the user attempts to reach a Russian-hosted site, the browser returns ERR_CONNECTION_TIMED_OUT. The error occurs because the TCP handshake never completes; TSPU drops the foreign-origin connection to a Russian IP address. Sites hosted on foreign IPs, such as certain RUVDS instances, load normally. The recommended fixes are to configure split tunneling so that .ru, .рф and .su domains bypass the VPN, or to route specific applications such as Edge outside the tunnel while keeping Chrome inside it.
Scenario 2: ERR_CERT_AUTHORITY_INVALID without VPN
Direct connections to major Russian banks produce ERR_CERT_AUTHORITY_INVALID. The sites now present certificates issued by the National Certification Center of the Ministry of Digital Development (NUC MinTsifry). Because Chrome, Edge, Safari and Firefox do not include this root in their trust stores, the connection is flagged as insecure. Affected domains include alfabank.ru, psbank.ru, vtb.ru and sberbank.ru. Users who confirm they are visiting the genuine site can proceed via the advanced settings warning, or they can install the MinTsifry root certificate on their operating system. Browsers that already trust the certificate by default include Yandex Browser, Atom and Chromium-Gost.
Scenario 3: Partial loading or ERR_CONNECTION_TIMED_OUT without VPN
Some pages fail to load images or scripts even without a VPN. The cause is TSPU fingerprinting of older browser versions. Updating Chrome or switching to Firefox usually resolves the issue.
Recommendations for site owners and developers
Administrators should disable TLS 1.3, enable HTTP/2 support, and, if SSH access to the server IP is also blocked, obtain a new IP address. Many newly provisioned Russian VPS addresses are already filtered by TSPU before any content is published.
Related articles
Kaspersky Container Security Earns FSTEC Russia Certification as Antivirus Protection Tool
Kaspersky Container Security has received official certification from FSTEC Russia under certificate number 5122 dated October 23, 2026. The product was validated as a means of antivirus protection and meets the regulator’s requirements at the fourth level of trust. It also complies with the protection profile of type B for the fourth class, designated IT.SAVZ.B4.PZ. The certification enables deployment of the solution in government information systems, personal data processing environments, critical information infrastructure facilities, and industrial control systems. Specific usage must still align with individual system requirements and the conditions stated in the certificate. The solution has been listed in the Russian software registry maintained by the Ministry of Digital Development since 2023. Primary audiences include government agencies, large enterprises, and industrial operators that rely on containerized workloads inside regulated perimeters.
Russian Lawmaker Clarifies Apple and Microsoft ORI Registry Listing Does Not Ban Products
State Duma deputy Anton Nemkin stated that the inclusion of Apple and Microsoft in Russia's ORI registry imposes standard data retention obligations without automatically prohibiting their products. The registry entry requires companies to store user information and message exchange records in Russia for three years and message content for up to six months. Nemkin emphasized that these rules apply equally to Russian and foreign digital market participants regardless of business scale or country of registration. The companies were added on October 2, 2026, while Google Meet has been listed since January 26. Although the status mandates data provision to authorized bodies in legally defined cases, the listing itself does not confirm that corporations will share Russian users' correspondence with the state. Non-compliance may trigger separate regulatory measures, but the deputy urged against exaggerating consequences through sensational headlines.
Russia Hands Out 2.2 Million Rubles in Data Leak Fines During First Half of 2026
Russian companies received 13 fines totaling 2.195 million rubles for personal data leaks between January and June 2026, according to new research from InfoWatch. This amount represents a 1.6-fold increase compared to the entire previous year, when total fines reached only 1.385 million rubles. The study shows that Russian penalties accounted for roughly 11 percent of the 115 global fines recorded during the same period. Approximately one quarter of the Russian cases involved violations caused by employee negligence. Organizations in the IT and information security, industrial, and trade sectors were fined most frequently. InfoWatch notes that turnover-based fines have not yet been applied and expects broader enforcement to begin in 2027.
Fines for Telegram Advertising May Be Delayed Beyond Transition Period
Russian authorities are reportedly considering delaying enforcement of new fines targeting advertisers in Telegram after the end of the announced transition period. According to sources cited by the Post- outlet, the government has not yet reached a clear decision on practical application of the advertising ban. Law enforcement agencies are also said to have stepped back from demanding strict punitive measures. Without official confirmation, advertisers and channel owners continue to operate under existing rules. The Federal Antimonopoly Service (FAS) had previously signaled stricter oversight starting in 2027, but current indications point to a possible extension of the status quo. Industry participants are advised to monitor developments closely as the situation remains fluid.