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
Kubernetes Audit Policy Review: Checklist Targets Common Blind Spots in Rules
An experienced Kubernetes administrator shared a detailed review process for audit policies that often remain untouched for years after initial deployment. The 580-line policy was rebuilt using the Kubernetes Threat Matrix from RedGuard as the primary reference. The author highlights recurring issues such as outdated exceptions, missing coverage for new components, and legacy comments that obscure actual security intent. The resulting checklist focuses on principles rather than cluster-specific findings to help other teams perform effective policy audits. Key recommendations address rule completeness, exception management, and periodic full-scale reviews instead of incremental patching. The approach aims to restore audit policies as active security controls rather than accumulated technical debt.
Avoiding a Leaky Kubernetes Audit Policy: Real-World Configuration Breakdown
Kubernetes Audit Policy is typically configured once during cluster setup and then left untouched for years while accumulating exceptions for new components. Over time the policy stops functioning as a security control and instead becomes an archaeological layer of outdated comments such as "# temporary, TODO remove" that date back three years or more. The author recently reviewed their own 580-line configuration file that had been assembled from multiple sources. Primary reference was the Kubernetes Threat Matrix, which explains why many rules are designed to detect security-relevant actions rather than simply reduce log noise. Examples include targeted monitoring of RBAC modifications and deletion of events. The article emphasizes the need for periodic full reviews instead of incremental patching to maintain effective detection coverage.
CryptoPro Develops CryptoPro-Browser with Russian Cryptography for FSB Compliance
CryptoPro is creating its own browser called CryptoPro-Browser as part of the CryptoPro CSP 6.0 cryptographic information protection system. The product will include built-in cryptographic tools, support for the company's plugin, and TLS connections using Russian cryptographic algorithms. The development follows Google's removal of the CryptoPro extension from the Chrome Web Store in February 2025, which left new users without an easy installation method. The project has been coordinated with the FSB of Russia and targets scenarios requiring compliance with Russian information security regulations. CryptoPro plans to incorporate experience from its earlier Chromium-Gost project started in 2017, while also recommending Yandex Browser as an alternative. Analysts estimate the development cost at several tens of millions of rubles, with the main focus on corporate customers needing certificate management and specialized support.
Yandex 360 Email Archive Documentation Shows Search Snapshots and Former Employee Log Filters
The Yandex 360 administrator guide describes the email archive as a tool that stores copies of all messages sent and received by employees on the organization's domain. Two specific statements in the documentation indicate that each saved search returns a static snapshot that does not update automatically when new mail arrives, requiring manual cloning or recreation of the search to obtain current results. The same documentation states that the action log records every operation performed in the archive, yet the employee filter in the log interface only displays currently active accounts, making it impossible to select a former administrator by name. API 360 currently provides no documented endpoints for creating, executing, or retrieving archive searches, leaving all operations dependent on the web console. Additional notes clarify that messages remain available after an account is blocked but disappear once the account is deleted, and that messages removed before the archive was enabled cannot be recovered. These documented behaviors directly affect incident response and offboarding procedures that rely on historical email retrieval and audit trails.