Can someone elaborate why this happens... more specifically, why friggin' Microsoft... lol
When I connect to scan cloud... I see 3 entries in my connections log, in this order:
https://who.is/whois-ip/ip-address/108.161.189.192
https://who.is/whois-ip/ip-address/104.45.231.79
https://who.is/whois-ip/ip-address/168.62.20.37
When I go through menu to check for updates... I see 1 more entry in my connections log, which is also spotted above:
https://who.is/whois-ip/ip-address/168.62.20.37
My question is... when did Zemana bump uglies and start working with Microsoft?
Fair enough, if one of the engines ZAM uses is from MS, I could sorta' accept seeing MS pop up. However, update checks too? I tried adding the 168.x.x.x entry to my ZAM firewall rule, to see if the previous two would buckle (and maybe cloud connection). Cloud connection stalled for a while, but it did connect. So, performed another update, managed to get both working on the one MS IP.
So, what gives? I used to use ZAL ages ago, but do not remember performing whois checks on IPs, so cannot confirm if this IP was MS-related back then. However, I can confirm that the IP does look the same from my ZAL days.
EDIT: The comments section for the 168.x.x.x report are ominous... also, I wonder how the ZAM Windows Service behaves...