3 ms·
If you see where the packets are going you might be able to block at the DNS level.
by yeck 3y ago
If you see where the packets are going you might be able to block at the DNS level.
- TacticalCoder 3y ago> If you see where the packets are going you might be able to block at the DNS level. There are many DNS blocklists out there and some of them do indeed block domain names from known telemetry (aka "spying") services. But if some telemetry directly report to specific IP addresses then blocking at the DNS level won't help. FWIW my firewall blocks some companies' known IP CIDR blocks (like FB/Meta) and my DNS (unbound) blocks all known malware, porn and telemetry services (among others). In addition to that the only process allowed to emit ongoing traffic to port 443 is the process running my browser. All hope is not lost yet.
- Tokumei-no-hito 3y ago> In addition to that the only process allowed to emit ongoing traffic to port 443 is the process running my browser. How did you get this configured?
- Dah00n 3y agoUnless they circumvent the system set DNS and use a hard coded one, which many that collect telemetry seem to do. On Android I see lots of traffic to Google's DNS even though I do not use their DNS servers (and it is in fact blocked).