TSPU

Troubleshooting Erroneous TSPU Blocks: How Admins Can Collaborate with Russian Regulators

A Moneta client outage traced back to erroneous filtering on Russia's TSPU system rather than internal infrastructure or DDoS protection. Engineers used curl, traceroute, nping, and custom Python scripts to confirm TCP payload-based blocking after the handshake. The team submitted a request via the VTS personal account, received partial acceptance status, then escalated to DCOA and SSOP to obtain the specific TSPU site number. Detailed network traces and active traffic were required for diagnostics. The case highlights coordination challenges between operators, DCOA, and SSOP when erroneous blocks occur on information resources.

Durev VPN Accused of Plagiarizing Independent Researchers' Articles for Commercial YouTube Promotion

Independent Russian cybersecurity researcher zarazaexe has publicly accused the commercial VPN service Durev VPN of systematically copying technical articles about Russian internet censorship systems, messenger analysis, and government-issued certificates. The team behind Durev VPN allegedly rewrote the original research into YouTube video scripts, replaced first-person statements with references to their own specialists, and removed all attribution to the source author or project. One video titled СРОЧНО УДАЛИ СЕРТИФИКАТ МИНЦИФРЫ reportedly gained 795,000 views in two days, while the service's Telegram bot shows 260,000 users and charges a minimum subscription of 313 rubles per month. Specific copied elements include scanning results of 46 million Russian IP addresses that yielded 63,000 entries in TSPU whitelists, architectural descriptions of default-deny and fail-closed policies, ECH handling by DPI systems, and detailed reverse-engineering findings from the MAX messenger client. The researcher documented the reuse of his earlier errors about UDP blocking inside whitelists and identical analogies comparing root certificates to apartment keys. When confronted, the Durev VPN representative initially demanded patents, invoked fair use, and later claimed the matter would be reviewed by their lawyer within a week. The researcher published the full chat logs and removed the disputed segment from one video after the complaint.

Russian TSPU Begins Intercepting UDP DNS Queries to Cloudflare and Google Public Resolvers

Starting on the evening of August 26, Russia's TSPU DPI system began actively intercepting plaintext DNS queries sent over UDP to public resolvers operated by Cloudflare and Google. Queries to 1.1.1.1 and 8.8.8.8 now return NXDOMAIN responses for blocked domains instead of the real IP addresses. The interception works exclusively on UDP; TCP-based DNS queries continue to receive legitimate answers from the original resolvers. Technical analysis shows the system performs targeted DNAT, rewriting the destination IP to the NSDI server at 195.208.5.1 only when a DNS query is detected inside the packet. Experiments with varying TTL values confirm that the redirection occurs after the traffic passes the TSPU node, and rapid successive queries can sometimes bypass the filter and return genuine records. The change affects netflow statistics visible to network operators, as traffic previously destined for foreign resolvers is now redirected domestically.

Why Legitimate Russian Websites Fail to Load With or Without VPN: TSPU RKN Blocking and MinTsifry Certificates Explained

Russian internet users are experiencing widespread access issues to legitimate domestic websites both when using VPNs and when connecting directly. The problems stem from TSPU devices installed by all ISPs under Roskomnadzor requirements and the transition to national MinTsifry certificates that foreign browsers do not trust. Three distinct error scenarios are documented: ERR_CONNECTION_TIMED_OUT when accessing Russian-IP sites over VPN, ERR_CERT_AUTHORITY_INVALID on major bank sites without VPN, and partial page loading failures caused by TSPU fingerprinting. Solutions for ordinary users include split-tunneling VPN clients, installing MinTsifry root certificates, or switching to Yandex Browser and Chromium-Gost. Website owners are advised to disable TLS 1.3, enable HTTP/2 support, and consider changing server IP addresses if SSH connections are also blocked. The article explicitly excludes any discussion of circumvention methods for prohibited content and focuses only on legal Russian resources as of August 2026.