Even with all the privacy, sync, and p2p settings off, using an offline account, I don't feel safe using Windows 10 for a business. I would like to restrict its ability to communicate to Microsoft (or vice versa) as much as I can.
Is there a list, or any way info out there, about what IP's Windows 10 is using to, for lack of better words, "phone home"? Or is there some way I can find/initiate the push listeners and see incoming? It seems mysteriously sparse in the resource monitor considering the amount of junk that's internet facing. I would like to block all possibilities of push/pull besides updates. However I don't know the plethora of "connected" services available in Win 10 yet and I feel that they would use massive ranges of IP's [v6] or proxies, which would be hard to capture fully. Or perhaps they may even mask com in some abstract layer, underneath the reach of monitors such as netstat or Fiddler.
So far I see some, svchost (netsvcs) perma connected occasionally calling system using the classic 22.214.171.124 range and some new IPv6, then there is system using MS limited in europe at 126.96.36.199 (I'm in USA), followed by system hitting MS denver 188.8.131.52. Im sure there are plenty more of these too that pop up. Also there are mysterious system connection bogons that are way out of our network range such as 169.254.255.255, and some other IP's I've seen checking in for just a second.
Do you know any more IP's like these? Any insights on how to force stop the non-essential communications or what to hardware firewall would be very much appreciated.