Can Wi-Fi Owners See Your Google Search History? HTTPS, DNS, SNI and ECH Explained
A short social media video went viral when a man complained on camera that no one had warned him Wi-Fi owners could see other users' search history. Influencer Kate Sarian reposted it with the comment that this was how privacy invasion looked today, prompting many users to question their assumptions.
Cybernews investigated the claim on 11 August 2026 and spoke with network engineers. The engineers stated that the panic was largely overstated, although not entirely unfounded.
What Physically Passes Through the Router
When a user types a Google search, the browser creates a URL of the form https://www.google.com/search?q=.... Until the connection enters TLS encryption, the path, query parameter, headers and cookies travel in plaintext. Once inside TLS, the router sees only the destination IP address, connection duration and data volume. No actual search terms are visible.
Three main metadata sources remain observable. Classic DNS queries on port 53 reveal domain names in plaintext. The Server Name Indication (SNI) field inside the TLS handshake also discloses the target domain. Finally, the router records MAC addresses, DHCP hostnames and connection timestamps, often displaying friendly names such as “iPhone of Natasha”.
ECH and the Last TLS Gap
After years of development, Encrypted Client Hello (ECH) was standardized as RFC 9849 on 3 March 2026. The mechanism hides the real domain name behind an outer unencrypted ClientHello that points to a CDN such as Cloudflare. Mozilla and Google Chrome added support in recent versions, yet Russian regulators began blocking ECH traffic in November 2024, causing widespread outages for ordinary sites hosted on Cloudflare.
The following table summarises visibility under different configurations:
- HTTPS + plain DNS: search text hidden, domain visible via DNS and SNI
- HTTPS + DoH/DoT: domain hidden from DNS but still revealed by SNI
- HTTPS + DoH + ECH: only the CDN operator visible
- Plain HTTP: full URL and search text may be readable
- VPN: local network sees only the VPN server
- Managed device with TLS proxy: full visibility possible
When Requests Are Actually Readable
The only practical cases where an administrator can read search queries involve either unencrypted HTTP (now under 5 % of traffic) or a corporate device that has had a root certificate installed by the organisation. In the latter scenario, the browser trusts the proxy certificate and the proxy can decrypt and inspect all traffic.
Google settled the Brown v. Google lawsuit in 2024, agreeing to update its Incognito mode warnings. The mode never hid activity from network administrators or employers.
Additional Observers in the Chain
Internet service providers in Russia must retain metadata for up to three years under the Yarovaya law package. Public Wi-Fi operators are required by Federal Law 97-FZ to identify users via passport or phone number. Search engines themselves receive every query in plaintext when the user is logged in.
Practical advice includes enabling DoH or DoT, keeping router firmware updated, avoiding installation of untrusted certificates, and using a reputable VPN when stronger protection is required.
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.