en.cryptonomist.ch
Google is preparing one of the more meaningful privacy shifts to hit Android in years, and it has nothing to do with a new camera feature or design overhaul. Starting with the next major release, Android 17 privacy encryption upgrades will hide the actual website domains people visit from network operators, internet providers and anyone else quietly watching traffic pass by. The change centers on a new standard called Encrypted ClientHello, or ECH, which Google says it is building directly into the operating system to close a surprisingly persistent gap in everyday web security.
Key takeaways
- Google will add Encrypted ClientHello (ECH) support in Android 17 to hide website domain names during the very start of a connection.
- Even on HTTPS sites, domain names are currently visible to network operators and eavesdroppers, allowing detailed user profiling.
- ECH scrambles the site name using a secret key that only the destination website can unlock.
- A companion feature called ECH GREASE, developed by Jigsaw, will be turned on by default in Android 17 to mask connection metadata even on sites that don’t yet support ECH.
- Full protection depends on websites and apps adopting the ECH standard, something Google says it is actively pushing with industry partners.
Android 17 Introduces Encrypted ClientHello for Enhanced Privacy
Encrypted ClientHello is designed to stop the very first handshake of a web connection from leaking which site someone is about to visit. Google confirmed the feature in an August 27 blog post, framing it as a direct response to how much metadata modern browsing still exposes, even when everything looks secure on the surface.
Bram Bonné, a Google software engineer, and Shuaibo Huang, an Android product manager, wrote that “when you visit a website or use an app, even if the connection is encrypted by HTTPS, the domain names of the sites we visit are still visible to network operators and eavesdroppers.” That single sentence sums up why Encrypted ClientHello exists in the first place. The two also warned that this kind of unencrypted metadata “can be used to build user profiles or, in the hands of malicious actors, leveraged for targeted phishing and scam campaigns.”
How ECH Encrypts Domain Names
ECH works by scrambling the destination website’s name at the very beginning of a connection, using a secret key that only the site on the receiving end can decode. In practical terms, that means a network operator watching traffic pass by no longer gets a clean readout of exactly which domain a device is contacting, even though the connection is still happening in real time.
Limitations of HTTPS in Concealing Domain Names
There’s a common misconception worth clearing up here: an address starting with “https” does not mean a connection is fully private. HTTPS relies on Transport Layer Security to encrypt the actual data traveling between a browser and a web server, and it does that job well. What it does not do is hide the domain name itself, and it offers no guarantee against a malicious site delivering malware or running a phishing scheme. The padlock icon protects the contents of a page, not the fact that someone visited it.
Google’s Collaboration to Accelerate ECH Adoption
ECH only works if the sites and apps on the other end of a connection actually support it, which is why Google is treating adoption as a shared industry problem rather than something it can solve alone inside Android. The company said plainly that “we are working with industry leaders, service providers, and app developers to accelerate ECH adoption.”
Industry Partnerships and Developer Engagement
That collaborative push matters because operating-system support and server-side support have to arrive together for the privacy benefit to show up for ordinary users. Google’s outreach to service providers and app developers is aimed at closing that gap faster than either side could manage on its own.
Role of Websites and Apps in Supporting ECH
Until a website or app implements ECH, connections to it won’t get the domain-hiding protection, regardless of how up to date a phone’s software is. This is the caveat Google itself flags, and it’s a reminder that Google Android security improvements at the device level still depend on cooperation further up the chain.
ECH GREASE Feature and Its Role in Privacy Protection
A second piece of the puzzle, developed by Jigsaw, addresses a subtler problem: if only some sites support ECH, then the presence of ECH itself becomes a signal that could be used to single out certain connections. The fix is a technique called ECH GREASE feature support, which papers over that gap by default.
How ECH GREASE Masks Connection Requests
Jigsaw explained that apps and browsers should send randomized, fake ECH extensions to sites that don’t actually support the real thing, specifically to avoid “exposing only certain connections as ECH-protected.” The effect is that every connection request looks identical from the outside, whether or not the destination site has adopted ECH yet.
Default Activation of ECH GREASE in Android 17
Jigsaw confirmed that starting with Android 17, “ECH GREASE will be enabled by default,” meaning users won’t need to flip any settings to get this baseline layer of protection against metadata profiling. Combined with full ECH support where it exists, this sets up a more consistent privacy floor across the browsing experience than Android has offered before.
Why does any of this matter beyond the technical detail? Domain-level metadata has quietly become one of the more overlooked pieces of the online surveillance puzzle, useful for building behavioral profiles even when the actual page content stays encrypted. By baking domain-hiding into the operating system itself rather than leaving it to individual apps or browsers, Google is effectively raising the default privacy floor for anyone running Android 17, without requiring users to understand what ECH even is.
FAQ
What is Encrypted ClientHello (ECH) in Android 17?
ECH is a privacy standard introduced in Android 17 that encrypts website domain names during connection initiation to hide them from network operators and eavesdroppers.
Why is HTTPS insufficient to protect my domain name privacy?
HTTPS encrypts data in transit but does not hide website domain names, which remain visible to network operators and can be used for user profiling.
How does ECH GREASE enhance user privacy?
ECH GREASE sends randomized fake ECH to sites that don’t support it, making all connection requests look uniform to prevent profiling based on connection metadata.
Does ECH work automatically on all websites and apps?
ECH requires websites and apps to support the standard; without adoption, users won’t get full protection.
Article produced with the assistance of artificial intelligence and reviewed by the editorial team.