Google Chrome mysteries

When checking network activity this weekend, I realized that without me using the computer, it was sending data somewhere, so I decided to close all programs.

However, even though there was no visible program, there was still traffic occurring at the exit door, so I decided to use a program to detect which process was using the network.

Then I realized that the "chrome.exe" process was still running (even visually terminated) and was accessing multiple internet addresses, and sending data.

I decided to close the process through the Windows Task Manager, and noticed that when reopening the Google Chrome browser, some connections were opened.

Here are the connections:

Understand the connections using the TCPView program:

After that, I decided to check what was really traveling, but I didn't get much information right away.

Notice that 1 byte was transferred to the server:

In a Google search, there is a topic on the subject, of which Google says that the address really belongs to their network, and which serves to ensure that the user is actually accessing the actual IP address of the site, as a supposed alternative to DNSSEC, to prevent attacks like Spoofing.

Google also reports that the service only works through Google products, such as,, among others.

1 comment: