Google Chrome’s Upcoming “IP Protection” Feature

Google is gearing up to pilot a new “IP Protection” feature in its Chrome browser, aimed at augmenting user privacy by concealing their IP addresses through the utilization of proxy servers.

With the revelation of possible misemployment of IP addresses for clandestine tracking, Google aims to find a middle ground between safeguarding user privacy and maintaining the indispensable functionalities of the web.

IP addresses serve as a tool for websites and online services to monitor user behavior across different websites, aiding in the development of enduring user profiles. This raises substantial privacy issues since, unlike third-party cookies, users at present have no straightforward method to avoid such surreptitious tracking.

Overview of Google’s IP Protection Feature

IP addresses, while being potential channels for tracking, are also crucial for pivotal web functions such as traffic routing, fraud deterrence, and other essential network activities.

The “IP Protection” feature tackles this dual nature by channeling third-party traffic from certain domains through proxies, thus rendering users’ IP addresses invisible to those domains. As the digital ecosystem transforms, the IP Protection feature will evolve to keep protecting users from cross-site tracking while including more domains in the proxy traffic.

According to a description of the feature, “Chrome is reintroducing a proposal to shield users against cross-site tracking through IP addresses. This proposal is a privacy proxy that anonymizes IP addresses for qualifying traffic as mentioned above.”

Initially, IP Protection will be an elective feature, empowering users to have dominion over their privacy while enabling Google to observe behavioral trends.

The rollout of this feature will be phased to consider regional aspects and ensure a learning curve.

Initial Deployment: Phase 0

In the initial phase, dubbed “Phase 0,” the feature will only affect listed domains in third-party contexts, focusing on those suspected of tracking users.

In this phase, Google will proxy requests solely to its own domains using a proprietary proxy to test the system’s infrastructure and refine the domain list. Initially, only users logged into Google Chrome and having US-based IPs will have access to these proxies.

A specific clientele will be automatically included in this initial test, with the design and architecture being refined as testing advances.

To prevent potential abuse, Google will operate an authentication server to allocate access tokens to the proxy, establishing a quota for each user.

Future Development: 2-Hop Proxy System

In the succeeding phases, Google envisages employing a 2-hop proxy system to bolster privacy further.

The idea is to utilize two proxies for enhanced privacy, with an external CDN running the second proxy while Google operates the first. This setup ensures that neither proxy can see both the client IP address and the destination, as detailed in the IP Protection explainer document.

GeoIP and Domain Testing

Many online services employ GeoIP to ascertain a user’s location for service provision. Google plans to assign IP addresses to proxy connections representing a “coarse” user location instead of a specific one.

Google intends to test this feature on its platforms like Gmail and AdServices, between Chrome versions 119 and 225.

Security Implications

Google acknowledges certain cybersecurity concerns regarding the new IP Protection feature.

Since traffic will be proxied through Google’s servers, it could pose challenges for security and fraud protection services in thwarting DDoS attacks or identifying invalid traffic.

Additionally, a compromise of Google’s proxy servers could allow malefactors to view and manipulate the transiting traffic. As a countermeasure, Google contemplates requiring users to authenticate with the proxy, disallowing proxies from associating web requests to particular accounts and introducing rate-limiting to thwart DDoS attacks.