Fri, Dec 11th 2020 1:38pm
Karl Bode
Each time you visit a website, your browser interacts with a domain name system (DNS) resolver that converts web addresses to an IP address understood by the machines along your path. Historically however this traffic exchange isn t encrypted, making it possible for your broadband provider or another third party to monitor your browsing data based on your DNS queries. DNS inventors in the 80s didn t really bet on a future where all DNS queries would be tracked, monetized, or weaponized by third parties.
Experts for a while have been arguing (including here at the Techdirt Greenhouse policy project) that it s important that we start encrypting these pathways to bring a little more security and privacy to the equation. Companies like Mozilla have been at the forefront of implementing DNS over HTTPS, a significant security upgrade to DNS that encrypts and obscures your domain requests, making it more difficult (though not impossible) to see whi
Fri, Dec 11th 2020 1:38pm
Karl Bode
Each time you visit a website, your browser interacts with a domain name system (DNS) resolver that converts web addresses to an IP address understood by the machines along your path. Historically however this traffic exchange isn t encrypted, making it possible for your broadband provider or another third party to monitor your browsing data based on your DNS queries. DNS inventors in the 80s didn t really bet on a future where all DNS queries would be tracked, monetized, or weaponized by third parties.
Experts for a while have been arguing (including here at the Techdirt Greenhouse policy project) that it s important that we start encrypting these pathways to bring a little more security and privacy to the equation. Companies like Mozilla have been at the forefront of implementing DNS over HTTPS, a significant security upgrade to DNS that encrypts and obscures your domain requests, making it more difficult (though not impossible) to see whi