The only IP where WFC should be allowed to connect is 184.108.40.206, and only when it checks for updates. Other connection attempts should be blocked, as they are generated by the operating system, not by WFC code. However, in the notification dialog context (when a new notification is displayed), WFC checks if the program has a digital signature. On other cases, the operating system checks if there is a valid certificate for WFC, or even referenced assemblies may check for a valid digital certificate. All these are made in the name of wfc.exe even if I don't trigger such verifications from WFC code. One thing is sure, WFC doesn't do any hidden activity on your system. No, WFC can't display the service name because this information is not available. If you have a new provider, different than the existing providers, I can add it into WFC list. In the past, this was editable, but many users didn't know the alternatives, so I made this as combo box with some predefined providers.