In light of recent criticism, Mozilla has decided against enabling DNS-over-HTTPS in the UK.
Allegedly, leaving it enabled would tie the hands of certain internet service providers and prevent them from blocking the domains they would not like their users to have access to. For example, if the website in question is hosting copyrighted material, child abuse footage or extremist material, it’s good practice for an ISP to block it.
In the UK, an ISP may receive a government request to performsuch blocking. However, another organisation may make the same request, for instance, a child protection group.
On the general side of things, Google and Mozilla have decided to make DNS-over-HTTPS an option. In Firefox, it has been a part of the browser since version 60. However, a user needs to activate it manually for it to take effect.
UK officials and child advocacy groups have raised concerns against it becoming the default option, as doing so would make decades worth of work go to waste. While the UK has listened to their pleas, the rest of Europe will follow a different course of action.
According to Mozilla, they are still exploring the partnership options to bring this important cybersecurity feature to Europeans. Moreover, the company’s stance is that the fears regarding DNS-over-HTTPS are exaggerated. They wish to emphasize that a more private DNS would not interfere with parental controls or the use of content filtering. They believe that DNS-over-HTTPS would offer increased cybersecurity benefits to UK residents.