I have been trying to figure out why Surf Protection would work in Firefox, but not in Chrome or Edge. As an example I used a website that is flagged as a privacy risk:
I noticed that Surf Protection blocked the site in Firefox.
It did not block the site in Chrome when built-in DNS client was enabled. Surf Protection did work when the built-in DNS client was disabled.
It did not block the site in Edge because it uses a built-in DNS client in the latest version of Windows 10 (1709) that does not depend on the system's DNS client because disabling it still allows Edge to resolve pages.
Is this something Emsisoft has been looking into? While disabling the built-in DNS client works, it comes at the cost of speed. Webpages take longer to resolve. It would be great if there was a way for EAM to catch queries of the built-in DNS clients these browsers have.