Sure, but there is really nothing to recreate:
1. You need an Apple Macintosh with "Little Snitch" installed:
I think they offer a limited time free trial. Its cheap enough, so I just purchased it.
It tracks and optionally blocks outbound network traffic. Note the 'outbound'. It is NOT a firewall.
I suggest checking that once installed LittleSnitch is set to "factory defaults" to get started.
2. Install epic bowser and fire it up. LittleSnitch will soon become a "pain in the ass" as it blocks and pops up
an alert on every outbound network connecton -- until you train it as to what to allow and what to block.
For example, using epic to just browse to this website to check this forum resulted in the following "epic wants to connect" alerts
that relate to google:
1. ssl.gstatic.com on TCP port 443 (https)
2. ssl.google.com on TCP port 443 (https)
3. safebrowsing.google.com on TCP port 443 (https)
4. alt1.safebrowsing,google.com on TCP port 443 (https)
5. sb1.google.com on TCP port 443 (https)
6. clients2.google.com on TCP port 80 (http)
<time spent typing this reply>
7. clients1.google2.com on TCP port 443 (https)
Some of these alerts are probably redundant, since I denied all these requests to connect. Note that these are only the connection
attempts that relate to google -- the other outbound connections, of which there were many, were allowed (for now).
is this traffic innocuous? I don't know. Thats the problem. I personally don't feel like running "Wireshark' to check every packet
of network traffic going out.
To be fair Chrome results in the same outbound traffic, so this is not a epic problem. But I think it does illustrate how much
information Google tries to capture from our web browsing.