Correct, If you were to use DNS over HTTPS to vist a plain text HTTP site your DNS would be protected but the content of the site wouldnt be, if your goal is privacy, the fact the site is in plain text would defeat that, and if the goal is prevent spoofing, plain text can easily be messed with.
When you browse to a site both the lookup for the site and the site itself needs to be protected for it to have any effect.
And for the second yup, DNS over HTTPs is a totaly differnt tech than DNS and runs on differnt "ports". Ports are numbers where your device "knows" to send traffic, and people hosting servers "know" what port to host on. HTTP is usually 80, HTTPS usually 443 and DNS usually 443
DNS has been around for years and runs on port 53. Every device knows how to talk this service and there are many providers of the service, your ISP, Google and cloudflare. Its plain text, but its just "works"
DNS over HTTPS is pretty new in tech terms and not much supports it, android 10, some browsers such as firefox, and some open source projects. It usually runs over port 443 to make it "look" like normal browsing and very few companies offer DNS over HTTPs servers. I dont think there is native support in Windows, Linux or iOS yet.
As they are running on differnt ports, Cloudflair offer both DNS (port 53) and DNS over HTTPS (port 443) for people to use. So you are using CloudFlair DNS on the Ipad, and CloudFlair DNS over HTTPS on the browser
Quote: Originally Posted by thydevil
AWESOME. Buy 1600 point card = $19.99. Buy two 800 point cards = $19.98
>XXX Quote: Originally Posted by someone153
Shhhh! Don't tell Microsoft. They might discover our secret.