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
US Department of Homeland Security Orders Federal Agencies to Remove DeepSeek Products
The US Department of Homeland Security issued an order on October 19 requiring federal civilian agencies to cease purchasing products from DeepSeek and to remove related technology from government systems. The directive, published the following day, targets Hangzhou DeepSeek Artificial Intelligence, its affiliates, and any third-party products or services built on DeepSeek implementations. The measure stems from the Federal Acquisition Supply Chain Security Act of 2018 and follows a recommendation by the Federal Acquisition Security Council, though no specific incidents or evidence were detailed in the notice. The restriction applies only to federal environments and does not prohibit private sector or individual use outside government systems. No removal deadline was set, and the document does not name the signing authority. The order is filed under docket DHS-2026-0628 with the CISA implementation team listed as the contact point.
AKIT Requests Temporary Permission for Russian Companies to Transfer Personal Data Abroad After Data Center Incidents
The Association of Internet Trade Companies (AKIT) has sent a formal letter to Russian Prime Minister Mikhail Mishustin proposing a temporary exemption from strict data localization rules. The measure would allow affected companies to move critical systems and Russian citizens' personal data to data centers in friendly countries when domestic infrastructure is unavailable due to accidents or damage. Members including Ozon, Wildberries, Cooper, and Yandex Market argue that services must continue operating even if Russian facilities are compromised. The proposed special regime would apply only after an officially confirmed incident, require compliance with information security standards, and end no later than March 1, 2028. After recovery, companies would be required to return to normal data processing within Russia. Expert Alexey Muntyan noted that the mechanism activates only after incidents occur and questioned whether countries should be selected based on data protection levels rather than political alignment.
Anthropic Model Reconstructs NSA Seeds for NIST Elliptic Curves in Under 30 Minutes
An internal Anthropic research model traced the origins of the five seeds used by the NSA to generate the NIST elliptic curves P-192, P-224, P-256, P-384, and P-521. The discovery resolves a 25-year-old question that arose when the curves were standardized in FIPS 186-2 for ECDSA in 2000. Researchers combined analysis of 1990s random number generators, 34 generator-output combinations, and lattice reduction techniques to identify lrand48 initialized with Unix timestamps from May 1997 to April 1998. The P-256 seed corresponds to the 1842nd candidate from a run started on 16 August 1997, and example seeds from ANSI X9.62 follow the same pattern. The work does not demonstrate any cryptographic break or backdoor in the curves and does not recommend changes to production systems. Several questions remain open, including the seed for curve B-163 and the reason certain candidate values were discarded.
Bitget Bans Residents of Russia, Kazakhstan and Belarus, Sets Strict Deadlines for Position Closure and Asset Withdrawal
Cryptocurrency exchange Bitget has updated its user agreement to prohibit residents of Russia, Kazakhstan and Belarus from using its services. The changes took effect on 16 October, with affected users receiving individual notifications via email, the mobile app and push alerts. New trading, orders and subscriptions were disabled at 10:00 Moscow time on 18 October. Users must close all positions and withdraw assets by 10:00 Moscow time on 21 October, after which remaining positions will be liquidated automatically and account access will be restricted. The exchange has not disclosed the specific reason for the decision in its public statement. The move underscores how access to crypto platforms can be terminated by changes in terms of service rather than technical issues or user credentials.