Page 2 of 2

Why does Google do this?

Posted: 10 Jul 2025, 22:34
by Duke
You should have sorted the list by the Process Name as I suggested, we may miss the bottom of the list in your first screenshot.

Anyway, we can see the established connections of Chrome:
142.250.190.3 : https://search.dnslytics.com/ip/142.250.190.3
Description Google LLC
PTR record ord37s32-in-f3.1e100.net

34.104.35.123 : https://search.dnslytics.com/ip/34.104.35.123
Description Google LLC
PTR record 123.35.104.34.bc.googleusercontent.com

And the closed ones [Time Wait]:
74.125.126.84 : https://search.dnslytics.com/ip/74.125.126.84
Description Google LLC
PTR record ik-in-f84.1e100.net

Chrome always connects to Google at launch. Always.
The only version I know which doesn't do it is Ungoogled Chromium.


Funnily LibreWolf is also showing connections to googleusercontent.com:
34.107.243.93 : https://search.dnslytics.com/ip/34.107.243.93
Description Google LLC
PTR record 93.243.107.34.bc.googleusercontent.com

That might be because of some extension, or maybe you added Google as your default search engine, or you have enabled Safe Browsing. But that's content from googleusercontent.com and not .1e100.net which is pure Google. I'm not getting those with LibreWolf on my computer.

But that's only 4 connections, not 77. And not telemetry to Mozilla.

Why does Google do this?

Posted: 10 Jul 2025, 23:12
by The-10-Pen
Cool!
I don't know what a PTR record is.
I did a "whois" on the IP address and it only showed Google, not "1e100.net".
So that's one issue solved.

On the LibreWolf issue, "your" tool doesn't show it (TCP). "My" tool does (DNS).
I always thought DNS was way more important than TCP.

I have no extensions installed in LibreWolf. Fresh "portable" download just today, ran in a VM that has never seen any browser beforehand.


Again, I always thought DNS was more important than TCP.
You missed one aspect of my post (or I forgot to mention it) - the SEVENTY SEVEN connections is FIRST LAUNCH ONLY.
Unless you carry over a profile to prevent them, then you have to run that first launch and allow those connections.
Subsequent launches only show these 12 DNS entries.

1.jpg
1.jpg (219.24 KiB) Viewed 202 times

Why does Google do this?

Posted: 11 Jul 2025, 07:36
by Duke
The-10-Pen wrote: 10 Jul 2025, 23:12 I don't know what a PTR record is.
I did a "whois" on the IP address and it only showed Google, not "1e100.net".
I took the time to provide links, why don't you take the time to click on them ?

The-10-Pen wrote: 10 Jul 2025, 23:12 On the LibreWolf issue, "your" tool doesn't show it (TCP). "My" tool does (DNS).
The World Wide Web is using TCP connections, that's it. It's how it works.

The-10-Pen wrote: 10 Jul 2025, 23:12 I always thought DNS was way more important than TCP.
You missed one aspect of my post (or I forgot to mention it) - the SEVENTY SEVEN connections is FIRST LAUNCH ONLY.
They are not connections, they are DNS queries.
The purpose of DNS servers is to resolve domain names into IP addresses that the browser can use. And these IP addresses are used in TCP connections, as said before.
That's why TCPView and CurrPorts are showing the real connections, I repeat: DNS queries are not connections to WWW servers.
You can also see these activities in about:networking in Mozilla browsers.

Why does Google do this?

Posted: 11 Jul 2025, 09:29
by The-10-Pen
Sounds great! Learning more and more each day.

I would put best-to-worst in this order -
1) IceCat [best but kind of "old"]
2) LibreWolf
3) R3dfox [bad but not worst]
4) Firefox [worst]