AntiMalware•August 26, 2026•🇷🇺Translated from Russian

Russian ISPs Begin Disrupting Encrypted DNS Services from Google and Cloudflare

Users of several major Russian internet providers have reported widespread issues accessing encrypted DNS protocols offered by Google and Cloudflare. The affected services include DNS over HTTPS (DoH) and DNS over TLS (DoT), which encrypt DNS queries and prevent providers from easily monitoring which domains users are visiting.

Measurements indicate that the filtering operates in a sophisticated manner. TCP connections are established successfully, but the secure tunnel is disrupted at the next stage. When connecting to Cloudflare addresses 1.1.1.1 and 1.0.0.1 on port 853, the TCP handshake completes, after which the connection is forcibly reset with an ECONNRESET error before TLS authentication finishes.

Google Public DNS shows a different pattern. Connections to dns.google, 8.8.8.8, and 8.8.4.4 on port 443 are established, yet after the TLS ClientHello is sent, responses stop. Sessions either hang until timeout or end with an "unexpected eof while reading" error. This behavior points to interference by intermediate network equipment using signature-based filtering.

The problems have affected subscribers of Rostelecom, Dom.ru, Tattelecom, and St. Petersburg-based SkyNet. Symptoms vary by operator and region: some users lose only DoT, others lose DoH, and some experience both protocols blocked. Tattelecom technical support reportedly advised one customer to disable both protocols to regain access.

Although no official statement confirming centralized blocking has been released, the simultaneous occurrence of identical issues across multiple providers and both major public DNS services makes random failure highly unlikely.

Related articles

Habr•Privacy & Surveillance

AWG Router Delivers Script-Free AmneziaWG Cascades with Load Balancing, Speed Limits and Leak Prevention

AWG Router is an open-source Python-based web panel that manages complex AmneziaWG VPN cascades without hundreds of lines of bash scripts. The tool generates nftables rules, ip rules, and tc queues to route Russian networks directly while sending other traffic through foreign AmneziaWG servers or SOCKS5 proxies. It enforces strict leak protection so that traffic never falls back to the entry server’s Russian IP when an upstream tunnel fails. The panel supports per-client routing policies, domain-based rules via SNI inspection, automatic load balancing across multiple exits, and granular speed limits using HTB and fq_codel. All state is stored in resilient JSON files, and the system continues operating even if the panel itself is restarted or updated. The project is released under the MIT license with full source available.

AntiMalware•Privacy & Surveillance

TV Manufacturers Admit They Cannot Fully Disable User Data Collection

The Verge surveyed 11 major television and streaming device makers about their data collection practices, receiving responses from seven companies including Amazon, Apple, Google, LG, Roku, Samsung and TCL. Automatic Content Recognition (ACR) technology, used for targeted advertising and audience measurement, remains a central concern, with Samsung, LG and Amazon disabling it by default. Google enables diagnostic and advertising data collection under standard settings, while Apple stated that Apple TV 4K does not employ ACR. Amazon, Google, Samsung and Roku acknowledged that complete opt-out from data transmission is impossible, with devices caching information offline for later upload. Research from Northeastern University revealed that Vizio continued sending data even after users declined collection, labeling it as operational telemetry. LG was found to potentially store unencrypted voice command transcripts and determine location via nearby Wi-Fi networks when ACR is active.

Habr•Privacy & Surveillance

Personal Data in Russian Franchise Networks: Who Qualifies as Data Operator Under 152-FZ

In typical franchise models, customer personal data is collected at franchisee points, stored in the franchisor’s central system, and used for network-wide loyalty programs and marketing. The key legal question is which party determines the purposes of processing and therefore bears operator status under Federal Law No. 152-FZ. The law defines an operator as the entity that independently or jointly sets processing purposes, data composition, and actions, regardless of contractual labels. Franchisees usually act as operators when concluding contracts with customers, while franchisors become processors unless they pursue independent goals such as running loyalty schemes or sending branded advertising. When a franchisor defines its own purposes, both parties may simultaneously qualify as operators for different processing objectives, requiring separate legal bases and documentation. Proper data-processing instructions must be embedded in the commercial concession agreement and must list specific data categories, actions, security measures, and breach-notification timelines to avoid administrative fines ranging from 150,000 to 500,000 RUB.

Habr•Privacy & Surveillance

Dynamic Sites on Yandex Cloud Storage Enable Communication Under White-List Restrictions

A developer facing mobile internet white lists explored ways to exchange encrypted messages without relying on blocked infrastructure. Initial attempts with a national messenger bot failed due to poor API documentation and account hijacking. The team then modeled the problem as three neighboring plots where Alice and Bob route messages through Eve while a slow postman handles delivery. Yandex Disk was tested as a message store accessible via direct GET and POST requests, though it required accounts and suffered from 15-25 second latency. The final approach used Yandex Cloud object storage, whose domains remained whitelisted, allowing HTML files to load and function even when only government services and select platforms were reachable.