Google rolled out new network security protections in Android 17 on Thursday, centered on a privacy standard that stops networks from seeing which websites users visit. The announcement detailed multiple features aimed at strengthening connection privacy, closing cellular security gaps, and protecting information about users' home networks. At the core of the update is system-wide support for Encrypted Client Hello (ECH), which conceals website destinations from anyone monitoring the connection.
The ECH feature operates alongside private DNS to mask domain names visited by users, encrypting the destination website name from the outset with a secret key that only the target site can unlock. Google's Jigsaw division explained that because not all web servers offer ECH compatibility, Android 17 enables ECH GREASE by default—a mechanism that transmits fake, randomized ECH extensions to sites lacking ECH support so every connection request appears identical. While ECH arrived in Google Chrome version 117 and Mozilla Firefox version 118, the Android 17 rollout extends the protection across the entire operating system rather than individual browsers. OkHttp, an open-source HTTP client, has also integrated ECH into its core library, letting third-party Android app developers tap into the capability.
According to Google's Bram Bonné and Shuaibo Huang, ECH "helps ensure that, for supported websites and apps, network providers and network snoopers can no longer easily see which websites or apps you are accessing." The update also introduces Local Network Protection, which requires apps to request user permission before scanning or connecting to other devices on the same local network. Two additional security measures include default activation of Certificate Transparency—forcing all websites to appear in a public registry—and a new option for telecom operators to disable 2G by default for their subscribers, blocking downgrade attacks and limiting exposure to rogue base stations or SMS blasters capable of sending malicious messages or intercepting traffic from nearby devices.
The ECH standard addresses a longstanding weakness in encrypted web traffic: even when HTTPS scrambles the content of a connection, the initial handshake historically revealed the destination domain in plain text, allowing internet service providers, corporate network administrators, and attackers to build profiles of users' browsing habits. By encrypting the Client Hello message at the start of a TLS connection, ECH closes that gap, leaving observers able to see only that a connection occurred—not where it went. The GREASE mechanism matters because partial deployment of any privacy technology creates a fingerprinting risk: if only ECH-enabled connections stood out, adversaries could infer that unprotected traffic belonged to sites lacking support. Sending fake ECH data to non-supporting servers ensures uniformity across all connections. The 2G shutoff feature tackles a different threat vector—attackers have long exploited the aging protocol's lack of mutual authentication and weak encryption to force modern phones onto vulnerable networks, then intercept calls and texts. Google noted that while Android 12 offered a manual 2G disable option and Android 14 gave IT administrators control over managed devices, the carrier-level toggle in Android 17 delivers a zero-click solution that "helps eliminate the legacy attack surface out of the box, proactively mitigating a primary method used by SMS blasters before they can target your device."
The Android 17 release signals Google's shift from app-level privacy patches to operating-system defenses that work regardless of which browser or third-party software a user runs, reducing the attack surface without requiring technical knowledge or manual configuration. By delegating 2G policy to carriers and making ECH GREASE the default, the update removes decision-making friction that has historically left most users exposed. The combination of encrypted handshakes, local-network permission prompts, certificate logging, and cellular protocol restrictions creates overlapping layers that raise the cost and complexity of surveillance—whether by commercial trackers, malicious actors, or state-sponsored adversaries. For enterprise buyers and security teams, the practical implication is that baseline privacy hygiene now ships in the platform rather than depending on user behavior or third-party tools. The move also pressures web server operators and carriers to adopt compatible standards or risk leaving their customers visibly less protected than competitors who do.