Is there any way to block connection to these sites with DNS or something?
Not at all.
11–20 of 296 posts
Is there any way to block connection to these sites with DNS or something?
Not at all.
Is there any way to block connection to these sites with DNS or something?
It can be easily configured to block any host or path.
Typing in https://r.bing.com/ from the list gives a interesting page.
Anyone feeling tempted to play the Devil’s advocate here? :)
Is there any way to block connection to these sites with DNS or something?
Someone else has some suggestions?
$ curl -fsSL 'https://helgeklein.com/blog/windows-os-services-apps-network-connection-target-hosts/' | pup 'td:nth-child(5)' text{} | sed 's/:.*$//' | sort -u | wc -l
291
$ curl -fsSL 'https://helgeklein.com/blog/windows-os-services-apps-network-connection-target-hosts/' | pup 'td:nth-child(4)' text{} | awk '{ s += $1 } END { print s }'
2764
There’s also a fair amount of infrastructural stuff such as DigiCert’s OCSP service, and every shard(?) in the Windows Update, OneDrive, etc. CDNs is counted as a separate hostname.Not that I’m happy about of any of these connections, but the report looks much less interesting than the totals alone suggest.
I wish to see this also for macOS, iOS and Android.
You can use it to watch every process send network traffic, you can even collect samples of the traffic and plot it on a map: https://www.obdev.at/products/littlesnitch/index.html
(not affiliated, just a happy customer; it's one of the few things I like the mac ecosystem for.. there's attempts to port it to linux with https://github.com/evilsocket/opensnitch; but it's not as polished of course)
Is there any way to block connection to these sites with DNS or something?
Disable DNS cache service so that all your apps resolve DNS themselves (can only be done via the registry, change the service's startup type from 2 (auto) to 4 (disabled)).
In CIS, create a new group for all files under c:/windows.
Create a rule denying all in/out requests to that group.
Create a rule allowing only DHCP and NTP requests (255.255.255.255:67 and :123) for svchost.exe (place that rule above the one for c:/windows to ensure precedence).
Use third-party utilities instead of the likes of ping.exe, e.g. hrping.
Refer to CIS documentation in case of any troubles.
Enjoy your privacy-hardened windows.