maltrail ofereix aquesta informació

http://check.googlezip.net/e2e_probe?q=76444f89-1459-487e-bbce-02bb2d7a6e05



10.1.133.208

39691

216.58.211.108

80 (http)

TCP

HTTP

potential proxy probe (suspicious)

(heuristic)

un ordinador a la xarxa wifi que vol connectra a googlezip.net

i no se que és?

cercant per google

https://developer.chrome.com/multidevice/data-compression-for-isps

Chrome Data Compression Proxy for Network Administrators, Carriers, and ISPs

Details

When Chrome starts with the DCP setting enabled, the DCP is enabled by the user, or a network interface change occurs, Chrome asynchronously issues an in-the-clear HTTP request to the canary URL, http://check.googlezip.net/connect.
There are three possible outcomes of the canary URL request:

• If the response status code is 200 and the response body is OK, Chrome uses an encrypted proxy connection for subsequent HTTP requests.
• If the response status code is anything other than 200 or the response body is anything other than OK, Chrome uses an unencrypted proxy connection.
• If the canary URL request times out or a DNS error occurs, Chrome uses an encrypted proxy connection.

Proxy Bypass

The Chrome DCP issues a proxy bypass response for URLs matching a list of restricted URLs maintained by Google. A proxy bypass causes Chrome to disable the use of SSL for the DCP connection for a short time (randomly chosen between 1 and 5 minutes). Carriers or network administrators can then block or take appropriate action on the request.
Proxy Bypass is used mainly for:

• Child sexual abuse material, which includes NCMEC, IWF and other lists used globally by Google for restricting access to such illegal material
• URLs subject to court-ordered DMCA and other takedowns on Google services
• Country-specific takedown lists, which are applied only to users with IP addresses originating in the associated country
• A small number of other sites known not to work well with the DCP (e.g., known carrier billing portal and intranet sites)

 més

https://support.opendns.com/hc/en-us/articles/227989047-Chrome-for-Mobile-and-OpenDNS-Inconsistency-with-block-pages

 

Overview

If you're seeing issues with inconsistent block page issues with Chrome for Mobile, please have your end user disable Chrome's Reduce Data usage feature.   As an example, you may see certain pages being blocked in Chrome for Mobile when they are not blocked on another browser on the same mobile device or allowed when unexpected.

When this feature is enabled, all HTTP traffic from Chrome for Mobile gets redirected to a Google proxy at this address: compress.googlezip.net. The proxy then compresses the data and sends it back to the client. Unfortunately, when this happens, the proxy will perform it's own DNS requests against it's own DNS servers, which causes inconsistent block page issues as the DNS services are no longer with OpenDNS.


multiples reports podem trobar 

https://www.fastvue.co/sophos/blog/google-data-saver-affect-security-confidentiality-reporting

How Google Data Saver affects web traffic logging and reporting

As you can imagine, Google Data Saver can cause havoc with your reporting as well.
Below are two screenshots from an Activity Report I generated using Fastvue Sophos Reporter to illustrate the effects. The first with Google Data Saver turned off, and the second with Google Data Saver turned on.

Google Data Saver Off

When accessing fastvue.co with Google Data Saver off, the HTTP content is correctly served from fastvue.co and logged and reported appropriately.

Google Data Saver On

With Google Data Saver turned on, all of the individual HTTP requests are gone, and all you see are HTTPS sessions to https://proxy.googlezip.net

Controlling Google Data Saver

Now you understand how Google Data Saver affects your visibility and control over your web traffic, you may be wondering how you can disable it in your network.


COMPROBEM A CASA AMB FIREFOX

http://check.googlezip.net/test.html


Chrome Compression Proxy not detected.
Response headers for the AJAX request to //check.googlezip.net/probe/image.jpg:

Accept-Ranges: bytes
Content-Type: image/jpeg
Access-Control-Allow-Origin: *
access-control-expose-headers: Via, X-Original-Content-Length, Chrome-Proxy
Content-Length: 643
Date: Mon, 10 Sep 2018 07:40:08 GMT
Pragma: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Cache-Control: no-cache, no-store, must-revalidate
Last-Modified: Thu, 21 Apr 2016 03:17:22 GMT
X-Content-Type-Options: nosniff
Server: sffe
x-xss-protection: 1; mode=block

Navigation timings:

dns: 0
con: 0
req: 34
rcv: 0
ntsrt: 68
nsfs: 2
ntplt0: 128

vull realment que al centre s'utilitzi el proxy per saltar els controls de navegació a google ?