It didn't happen a lot, but it did happen.Īfter a few months I restored defaults then uninstalled and reinstalled Firefox and still had the problem so I started to investigate. I thought I had just broke a setting in Firefox somewhere. Randomly in Firefox, some websites just would fail to load saying that there was a problem with that website's certificate. This also happened to me with avast a few years ago. I'm not saying it's good of Avast to rely on other companies for their service, but you have to be paranoid to think that someone at Google is spying on your life through Avast link safety checks.
So don't run around with your tinfoil hats and do some research instead. Seems like Avast is cheap enough to just send every link you visit to Google for link safety check.Įdit: forgot to mention, if you turn web shield off the connections are gone immediately and the only thaffic from Avast is done to their servers. I think at this point, if you have ever used Avast, you've already figured out that it's the Web shield component that uses those connections. That feature checking sites and tell you if that site is "Attack Site" Q: What is and why do I have TCP ports open to it?Ī: It's Google Safebrowsing feature in Chrome. A quick search brings up this question and answer: Well, there seems to be some connections to (IP 64.233.166.109). The main spook seems to be about Google servers. If you stop that shield the connections are gone. Okay, for everyone lazy I did some scanning with CurrPorts and some googling (using DuckDuckGo and not Google) and here's the results:Īvast opens some ports from 127.0.0.1 to 0.0.0.0 (that means locally) for it's mail shield.