5 ms·
Bare in mind, when using DNSCrypt with OpenDNS you're actually reducing your overall level of privacy. Now two companies can see what sites you're visiting: you
by mike-cardwell 13y ago
Bare in mind, when using DNSCrypt with OpenDNS you're actually reducing your overall level of privacy. Now two companies can see what sites you're visiting: your ISP and OpenDNS.
Your ISP doesn't need to see your DNS queries in order to know what sites you're visiting. They can see the IP's that you're sending packets to. They can see the HTTP "Host" header for HTTP. They can even see the hostname for HTTPS because of SNI.
- pstack 13y agoThree. Don't forget the website, itself. Well, maybe four or five or ten. Don't forget all of the advertisements and beacons on the site you're visiting. Well, maybe also Google, if you're using Chrome. Oh, and maybe everybody, unless everything you're doing is always encrypted and it's through a VPN service that doesn't maintain any logging and isn't subject to government subpoena and can be thoroughly trusted. Frankly, if your ISP can see it, then who cares who else along the chain does? Nobody else providing a service that can see your data is going to do anything with it that Comcast, Cox, Sprint, Verizon, AT&T, CenturyLink, and Frontier isn't already doing.
- mike-cardwell 13y agoNone of the examples you have supplied are equivalent or relevant. My point stands: If you use DNSCrypt+OpenDNS in order to try and hide your browser history from your ISP, not only will you not succeed, but you will make matters worse.
- pstack 13y agoRight. My point was simply that there's little point to them being concerned about their ISP in the first place if they're exposed elsewhere along the chain (unless they're simply worried about being locked-down from accessing certain servers for some reason, I guess?).