Google Android 17 Hides Website Names From Network Observers
In brief
- Android 17 enables Encrypted Client Hello by default, hiding website names from network observers
- ECH encrypts the SNI field so only destination servers can read which sites users visit
- Protection only works for sites that have adopted ECH; unsupported sites still expose domains
- Android 17 also enables Certificate Transparency and requires local network scanning permissions
How Encrypted Client Hello Works
Encrypted Client Hello encrypts the site name to a key the destination publishes, and only that server can unwrap it. The rest of the path sees a meaningless label instead of the domain.
It's a straightforward idea. But the rollout has a catch.
The Limitation
ECH protects traffic only to destinations that have adopted it. Requests to sites without the standard still show their domain to the network. That means adoption matters. A user visiting an ECH-enabled site gets the privacy win. A user visiting an older site doesn't.
Even when the site name is hidden, the network still sees the destination server's IP address and the volume of data moving. An observer can infer activity at a coarse level—someone's browsing video, or reading text, or streaming—without knowing exactly where.
Other Privacy Changes in Android 17
Google didn't stop with Encrypted Client Hello. Android 17 also turns on Certificate Transparency by default and requires apps to ask permission before scanning a local network. Certificate Transparency logs the creation of SSL certificates, making it harder for attackers to issue fake certs without detection.
