Russian TSPU Systems Redirect DNS Queries to Google and Cloudflare Servers Toward National Domain Name System
Since the evening of August 26, Russian TSPU (technical means of countering threats) have started redirecting open DNS queries addressed to Google and Cloudflare public DNS servers toward the National System of Domain Names (NSDI). The change affects users of multiple Russian internet providers and coincides with ongoing implementation of content filtering systems required by Russian legislation.
When a standard UDP DNS query is sent to addresses such as 8.8.8.8 or 1.1.1.1 for domains including YouTube and RuTracker, the response returned is NXDOMAIN, indicating that the domain does not exist. In contrast, identical queries sent over TCP successfully reach the original servers and obtain genuine IP addresses.
Further traffic analysis by Habr user angry_agent showed that packets with a deliberately low TTL value elicited ICMP TTL Exceeded messages containing the IP address 195.208.5.1, which belongs to NSDI. The same behavior was not observed with arbitrary UDP packets, confirming that the system specifically inspects DNS traffic.
According to the researcher, TSPU devices recognize open DNS queries and perform a directed DNAT operation, transparently altering the destination address so that the packet is delivered to an NSDI server. The national resolver then decides what response to return to the user. From the perspective of the network operator, the query appears to have been sent directly to NSDI rather than to a foreign resolver.
The mechanism is not flawless. When several identical queries are transmitted rapidly, the first request receives an NXDOMAIN response while subsequent requests reach Google and return correct addresses. Redirection also does not occur for every public DNS server tested.
No official statement confirming the new redirection technique has been issued by Russian authorities or network operators. The conclusions are based solely on the experiments of a single researcher. The development follows reports from users of several Russian providers who experienced difficulties accessing protected DNS services operated by Google and Cloudflare.
Related articles
WebRTC IP Leaks Explained: Why Disabling the Protocol Harms Anonymity in Anti-Detect Browsers
The article from Aurorium details how WebRTC technology can leak real IP addresses even when users route traffic through proxies. It explains the peer-to-peer mechanics of WebRTC, the role of STUN servers in generating ICE candidates, and why standard TCP proxies fail to handle UDP traffic. Disabling WebRTC via flags or JavaScript extensions creates detectable anomalies that anti-fraud systems flag as non-standard environments. The recommended approach involves native emulation inside the browser kernel so that STUN requests return proxy IPs while preserving full API integrity across workers. Additional leaks through local network addresses, mDNS candidates, and IPv6 are also covered with practical verification methods using tools like BrowserLeaks and CreepJS.
Docx Anonymizer: Open-Source Chrome Extension Uses Fine-Tuned rubert-tiny2 to Anonymize Personal Data Before AI Uploads
A Russian developer has released Docx Anonymizer, a browser extension that automatically detects and replaces personal data in documents using a lightweight NER model before they reach public AI services such as ChatGPT. The tool was created to help organizations comply with Russia’s 152-FZ personal data protection law while avoiding the risks of uploading contracts and other sensitive files to cloud-based LLMs. It runs entirely locally via ONNX Runtime and WebAssembly, requires no network calls, and supports any AI chat interface. The underlying model, rubert-tiny2, was further trained through knowledge distillation on WikiANN, factRuEval, and synthetic business documents, reaching strong F1 scores for person and organization entities after int8 quantization. The extension intercepts text on the fly, performs named-entity recognition in under two seconds for typical contracts, and replaces detected entities with placeholders. The project is fully open source and designed for minimal user friction, addressing the growing problem of employees inadvertently leaking corporate and personal data to public AI platforms.
Hybrid Post-Quantum Message Sealing: X25519 + ML-KEM-1024 in Umbera Messenger with Public Rust Tests
Umbera messenger has open-sourced its cryptographic core and published seven Rust tests that anyone can run to verify its hybrid post-quantum message sealing scheme. The design combines X25519 with ML-KEM-1024 so that an attacker must break both algorithms to decrypt a message. Messages are protected by Double Ratchet for forward secrecy, sealed sender packaging, and per-message ephemeral keys derived via HKDF-SHA256 into AES-256-GCM. The relay server stores only an opaque box identifier and encrypted blob with no sender or recipient fields visible. Media calls use DTLS-SRTP end-to-end while TURN servers see only encrypted datagrams. Addresses for message boxes rotate weekly and are derived solely from the shared secret between the two parties.
Free Ad Blocker for iPhone, Android, and Desktop Uses DNS Parsing Without Libraries and Skips YouTube Influencer Ads From the First Second
A new free ad-blocking solution has been released for iPhone, Android, and desktop platforms. The tool relies on a lightweight DNS parser that operates without external libraries. It includes a dedicated mode for users who already run VPN connections. An accompanying browser extension automatically skips sponsored segments in YouTube videos, even when the advertisement begins at the zero-second mark. The developer describes the technical challenges encountered after launch and the fixes applied to maintain compatibility across operating systems. The project emphasizes user privacy by avoiding unnecessary data collection and third-party dependencies.