Zillion connections to Google, Amazon, Twitter and others when Firefox opened after deleting cached files

I noticed that when I opened my Firefox browser (58.0.2 64-bit Linux), the connection light on my router kept blinking for a long time. I did a netstat -t command to find out to what I was connecting. To my surprise, it was a LOT more than Google.

It apparently has something to do with deleting cached files or folders, as I show later.

Here is an approximate listing of what I should see (all of the “sea15” servers are Google):
tcp 0 0 JW-PC:46562 server-13-32-178-:https ESTABLISHED
tcp 0 0 JW-PC:54168 sea15s12-in-f195.:https ESTABLISHED
tcp 0 0 JW-PC:49378 sea15s07-in-f68.1:https ESTABLISHED

Instead, here is a listing of what I saw. I’ve bolded some of the text:
tcp 0 0 JW-PC:56480 a23-32-46-41.deplo:http ESTABLISHED
tcp 0 0 JW-PC:33474 server-13-33-147-:https ESTABLISHED
tcp 0 0 JW-PC:45466 ec2-54-213-234-15:https TIME_WAIT
tcp 0 0 JW-PC:56334 151.101.2.202:http ESTABLISHED
tcp 0 0 JW-PC:34470 159.127.41.189:https TIME_WAIT
tcp 0 0 JW-PC:34040 a104-126-1-33.depl:http ESTABLISHED
tcp 0 0 JW-PC:53200 a23-45-230-178.de:https ESTABLISHED
tcp 0 0 JW-PC:58400 e2.ycpi.vip.swb.y:https ESTABLISHED
tcp 0 0 JW-PC:49226 sea15s01-in-f10.1e:http ESTABLISHED
tcp 0 0 JW-PC:51302 server-13-33-151-6:http ESTABLISHED
tcp 0 0 JW-PC:47918 sea15s11-in-f14.1e:http ESTABLISHED
tcp 0 0 JW-PC:60236 server-13-33-147-3:http ESTABLISHED
tcp 0 0 JW-PC:33614 a104-126-1-33.depl:http ESTABLISHED
tcp 0 0 JW-PC:53944 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:51256 151.101.193.128:http ESTABLISHED
tcp 0 0 JW-PC:51990 151.101.192.204:http ESTABLISHED
tcp 0 0 JW-PC:50912 server-13-33-146-6:http ESTABLISHED
tcp 0 0 JW-PC:51992 151.101.192.204:http ESTABLISHED
tcp 0 0 JW-PC:34268 server-13-33-151-:https ESTABLISHED
tcp 0 0 JW-PC:37506 sea15s01-in-f130.:https ESTABLISHED
tcp 0 0 JW-PC:47854 server-13-33-147-1:http ESTABLISHED
tcp 0 0 JW-PC:55610 sea15s07-in-f68.1:https ESTABLISHED
tcp 0 0 JW-PC:34062 sea15s07-in-f14.1:https ESTABLISHED
tcp 0 0 JW-PC:53384 sea15s07-in-f14.1e:http ESTABLISHED
tcp 0 0 JW-PC:39098 a23-204-103-59.dep:http ESTABLISHED
tcp 0 0 JW-PC:58614 sea15s11-in-f162.1:http ESTABLISHED
tcp 0 0 JW-PC:47124 server-13-33-151-1:http ESTABLISHED
tcp 0 0 JW-PC:47538 a23-6-165-175.depl:http ESTABLISHED
tcp 0 0 JW-PC:32878 a23-45-230-178.dep:http ESTABLISHED
tcp 0 0 JW-PC:38836 a23-217-12-72.depl:http ESTABLISHED
tcp 0 0 JW-PC:37574 104.19.193.102:https ESTABLISHED
tcp 0 0 JW-PC:37778 server-13-33-124-:https ESTABLISHED
tcp 0 0 JW-PC:48128 static.criteo.net:https ESTABLISHED
tcp 0 0 JW-PC:54364 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:53278 a.tribalfusion.com:http ESTABLISHED
tcp 0 0 JW-PC:40764 a23-14-172-134.de:https ESTABLISHED
tcp 0 0 JW-PC:42124 23.101.203.117:http ESTABLISHED
tcp 0 0 JW-PC:59364 ec2-54-225-214-20:https ESTABLISHED
tcp 0 0 JW-PC:54374 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:59902 server-13-33-151-:https ESTABLISHED
tcp 0 0 JW-PC:54736 a1.ue.vip.gq1.yah:https ESTABLISHED
tcp 0 0 JW-PC:49646 sea15s01-in-f10.1e:http ESTABLISHED
tcp 0 0 JW-PC:38936 a104-109-200-201.d:http ESTABLISHED
tcp 0 0 JW-PC:51672 sea15s01-in-f142.:https ESTABLISHED
tcp 0 0 JW-PC:52276 bam-9.nr-data.net:https ESTABLISHED
tcp 0 0 JW-PC:44270 151.101.66.2:http ESTABLISHED
tcp 0 0 JW-PC:42024 ec2-35-162-179-12:https ESTABLISHED
tcp 0 0 JW-PC:59886 152.195.32.112:http ESTABLISHED
tcp 0 0 JW-PC:45134 151.101.53.128:http ESTABLISHED
tcp 0 0 JW-PC:50914 server-13-33-146-6:http ESTABLISHED
tcp 0 0 JW-PC:35590 sea15s01-in-f10.1:https ESTABLISHED
tcp 0 0 JW-PC:51330 ec2-52-52-244-13.u:http ESTABLISHED
tcp 0 0 JW-PC:53916 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:57792 152.195.14.100:http ESTABLISHED
tcp 0 0 JW-PC:32934 ec2-54-164-46-184:https TIME_WAIT
tcp 0 0 JW-PC:54372 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:45136 151.101.53.128:http ESTABLISHED
tcp 0 0 JW-PC:59458 xx-fbcdn-shv-01-s:https ESTABLISHED
tcp 0 0 JW-PC:38240 40.84.148.247:http ESTABLISHED
tcp 0 0 JW-PC:37996 199.96.57.6:http ESTABLISHED
tcp 0 0 JW-PC:42556 23.101.203.117:http ESTABLISHED
tcp 0 0 JW-PC:58066 r-199-59-148-23.t:https ESTABLISHED
tcp 0 0 JW-PC:52060 ec2-54-213-128-13:https TIME_WAIT
tcp 0 0 JW-PC:53248 ec2-52-52-174-199:https TIME_WAIT
tcp 0 0 JW-PC:45300 sea15s07-in-f2.1e1:http ESTABLISHED
tcp 0 0 JW-PC:46038 104.16.87.26:https ESTABLISHED
tcp 0 0 JW-PC:48748 234.250.178.107.bc:http ESTABLISHED
tcp 0 0 JW-PC:60442 server-13-33-151-:https ESTABLISHED
tcp 0 0 JW-PC:49114 server-13-33-147-8:http ESTABLISHED
tcp 0 0 JW-PC:43940 s3-1.amazonaws.co:https TIME_WAIT
tcp 0 0 JW-PC:55376 sea15s07-in-f67.1:https ESTABLISHED
tcp 0 0 JW-PC:54368 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:46308 151.101.53.208:http ESTABLISHED
tcp 0 0 JW-PC:40772 a23-14-172-134.de:https ESTABLISHED
tcp 0 0 JW-PC:38888 a23-217-12-72.depl:http ESTABLISHED
tcp 0 0 JW-PC:43338 server-13-33-110-2:http ESTABLISHED
tcp 0 0 JW-PC:41848 server-13-33-151-1:http ESTABLISHED
tcp 0 0 JW-PC:60904 sea15s01-in-f3.1e:https ESTABLISHED
tcp 0 0 JW-PC:54116 ads16-fw-us-west.:https TIME_WAIT
tcp 0 0 JW-PC:38854 152.163.13.22:http ESTABLISHED
tcp 0 0 JW-PC:50086 ec2-50-17-199-221.:http ESTABLISHED
tcp 0 0 JW-PC:51902 151.101.192.204:http ESTABLISHED
tcp 0 0 JW-PC:32794 server-13-33-151-:https ESTABLISHED
tcp 0 0 JW-PC:41126 ec2-54-76-91-81.e:https TIME_WAIT
tcp 0 0 JW-PC:42880 74.121.143.236:http ESTABLISHED
tcp 0 0 JW-PC:48318 sea15s11-in-f162.:https ESTABLISHED
tcp 0 1 JW-PC:37396 162.248.16.50:http FIN_WAIT1
tcp 0 0 JW-PC:53922 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:46346 151.101.53.208:http ESTABLISHED
tcp 0 0 JW-PC:59598 152.195.32.119:http ESTABLISHED
tcp 0 0 JW-PC:60802 104.16.88.20:http ESTABLISHED
tcp 0 0 JW-PC:33258 server-13-33-151-1:http ESTABLISHED
tcp 0 0 JW-PC:58754 sea15s11-in-f162.1:http ESTABLISHED
tcp 0 0 JW-PC:59376 152.195.32.112:http ESTABLISHED
tcp 0 0 JW-PC:53920 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:42534 23.101.203.117:http ESTABLISHED
tcp 0 0 JW-PC:39818 72.21.91.66:http ESTABLISHED
tcp 0 0 JW-PC:53292 a.tribalfusion.com:http ESTABLISHED
tcp 0 0 JW-PC:51304 server-13-33-151-6:http ESTABLISHED
tcp 0 0 JW-PC:46356 151.101.53.208:http ESTABLISHED
tcp 0 0 JW-PC:54370 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:38886 a23-217-12-72.depl:http ESTABLISHED
tcp 0 0 JW-PC:51448 ocsp.comodoca.com:http TIME_WAIT
tcp 0 0 JW-PC:56056 xx-fbcdn-shv-01-s:https ESTABLISHED
tcp 0 0 JW-PC:59350 tags.expo9.exponen:http ESTABLISHED
tcp 0 0 JW-PC:40414 edge-star-mini-sh:https ESTABLISHED
tcp 0 0 JW-PC:45406 www2.twitter.jp:https ESTABLISHED
tcp 0 0 JW-PC:52934 74.119.119.70:https ESTABLISHED
tcp 0 0 JW-PC:55496 ec2-54-191-241-24:https ESTABLISHED
tcp 0 0 JW-PC:33036 a23-32-46-98.deplo:http ESTABLISHED
tcp 0 0 JW-PC:53028 ec2-52-72-47-138.c:http ESTABLISHED
tcp 0 0 JW-PC:39806 72.21.91.29:http TIME_WAIT

Today I also saw a connection to “download.apowersoft.net”

Not sure what is happening to cause this, or why I’m seeing so many connections to things that have no bearing to google (the home page), but it is concerning. I have not tried a different OS, but will do so at work. It doesn’t happen all the time with my own system, but is consistent if I remove the cached files from Firefox and then start the browser.

If I do not removed the cached files and folders, then it looks fairly normal:
tcp 0 0 JW-PC:41324 72.21.91.29:http ESTABLISHED
tcp 0 0 JW-PC:59650 sea15s01-in-f3.1e:https ESTABLISHED
tcp 0 0 JW-PC:42008 ec2-54-191-46-28.:https ESTABLISHED
tcp 0 0 JW-PC:56694 sea15s01-in-f14.1e:http ESTABLISHED
tcp 0 0 JW-PC:46844 a23-204-103-74.dep:http ESTABLISHED
tcp 0 0 JW-PC:52824 server-13-32-178-:https ESTABLISHED
tcp 0 0 JW-PC:57186 ec2-54-148-143-13:https ESTABLISHED
tcp 0 0 JW-PC:54158 sea15s11-in-f164.:https ESTABLISHED
tcp 0 0 JW-PC:41318 72.21.91.29:http ESTABLISHED

For some reason, Firefox generates a ton of connections to seemingly random (but probably not random) servers if the cache files are missing. It should simply create the folders without needing to connect to anything other than the home page, in this case Google.com

I don’t have any news feeds, and the “random” servers are different each time.

I will try asking in a forum about this.

UPDATE:
I found someone had asked a similar question on Mozilla’s forum:
https://support.mozilla.org/en-US/questions/1205150

He links the issue to the webappstore.sqlite file, but even so, it is a mystery yet not answered by Mozilla as to WHY this file has all of these connections to odd servers, even if the file is delete and auto-recreated. The poster says:

“Why does Firefox connect to every single address while starting up, what is written to this sql db? I could say this is the solution at least solving the original question “where does this software get it’s 100-400 connection addresses”.

So this seems to be the source of some of the issue, but where does Firefox get the server names in the first place?

 I found that I could turn off my permissions to the file webappstore.sqlite, and that stopped the connections to odd servers, but then I was unable to do things like edit my WordPress website. So clearly it is needed for some things, and I need to be able to write to it.
I think Mozilla should offer an explanation of what is happening and why the browser needs to connect to these hundred or so servers.