Reply to thread

Message

<blockquote data-quote="marzametal" data-source="post: 397930" data-attributes="member: 23627">Can someone elaborate why this happens... more specifically, why friggin&#039; Microsoft... lolWhen I connect to scan cloud... I see 3 entries in my connections log, in this order:<a href="https://who.is/whois-ip/ip-address/108.161.189.192" target="_blank">https://who.is/whois-ip/ip-address/108.161.189.192</a><a href="https://who.is/whois-ip/ip-address/104.45.231.79" target="_blank">https://who.is/whois-ip/ip-address/104.45.231.79</a><a href="https://who.is/whois-ip/ip-address/168.62.20.37" target="_blank">https://who.is/whois-ip/ip-address/168.62.20.37</a>When I go through menu to check for updates... I see 1 more entry in my connections log, which is also spotted above:<a href="https://who.is/whois-ip/ip-address/168.62.20.37" target="_blank">https://who.is/whois-ip/ip-address/168.62.20.37</a>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&#039; 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...</blockquote>

[QUOTE="marzametal, post: 397930, member: 23627"] 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: [URL]https://who.is/whois-ip/ip-address/108.161.189.192[/URL] [URL]https://who.is/whois-ip/ip-address/104.45.231.79[/URL] [URL]https://who.is/whois-ip/ip-address/168.62.20.37[/URL] When I go through menu to check for updates... I see 1 more entry in my connections log, which is also spotted above: [URL]https://who.is/whois-ip/ip-address/168.62.20.37[/URL] 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... [/QUOTE]

Verification