DNS over HTTPS adoption accelerates across major browsers

DNS over HTTPS is no longer a niche browser setting. It has become a normal part of the browser stack in Chrome, Firefox, Edge, Brave, and other major browsers, with Firefox pushing it by default in more regions and Chrome and Edge offering secure DNS settings that can turn on when conditions fit. The broad pattern is clear: encrypted DNS is moving from an opt-in privacy feature to a common default path.

I keep coming back to the same point: this is not one browser making a loud privacy choice. It is several browsers moving in the same direction, each in its own way. Firefox has been the most direct about it, with default rollout already in the U.S. and Canada and more countries still coming online. Chrome and Edge are less blunt, but they now support secure DNS in a way that many users will run into without looking for it.

That matters because DNS is the first lookup in a normal web visit. It turns a name like a domain into an IP address. When that lookup is sent in plain text, networks can see more than many users expect. DNS over HTTPS wraps that lookup in HTTPS, so the request is harder to read or change in transit.

For a domains and DNS reader, the practical shift is simple. Browser DNS is no longer only a server-side choice or a router setting. The browser itself may now decide to use encrypted DNS, and that can change how traffic is resolved even when the rest of the network has not changed. That is part of why the topic keeps coming up in hosting and DNS support. The browser is becoming an active part of the DNS path.

The major browsers are not identical here, and that is where the story gets less neat. Firefox has been the most aggressive with default DoH rollout in some regions. Chrome and Edge tend to offer secure DNS through settings and can use it when the provider supports it. Safari is the outlier in many current guides, with no clear browser-side DoH control in the same style as the others, and system-level DNS behavior still matters there. So yes, adoption is accelerating, but the user experience is still uneven.

That unevenness is the main caveat. DoH does not mean the same thing in every browser, and it does not behave the same way on every device, network, or DNS provider. A site owner may see encrypted lookups from one browser and plain lookups from another. A business network may also block or manage it differently from a home setup. The trend is strong, but the result is not universal.

There is also a trade-off that gets less attention than the privacy pitch. Browser-based DoH can improve privacy against local snooping, but it can also make DNS policy harder to enforce in some managed settings. That does not make it bad. It just means the browser is taking on more control, and control always has a cost. For hosting teams, that can affect how DNS filtering, parental controls, or enterprise rules behave in practice.

From a site operations view, the useful takeaway is not panic. It is awareness. DNS is becoming more encrypted by default in the browser layer, and that changes what support teams should assume when they look at a user report. A page that fails to resolve, or a security tool that sees different DNS behavior, may not be caused by the website itself. The browser may be doing exactly what it was built to do.

I also think the timing matters. Browser makers are not adding DoH as a one-off feature anymore. They are folding it into a wider move toward encrypted web traffic, tighter privacy controls, and more automatic security choices. That does not remove the need for clean DNS setup on the domain side. It just means the browser is now part of the DNS story in a bigger way than before.

So the headline is accurate. DNS over HTTPS adoption is accelerating across major browsers, and that shift is already visible in Firefox defaults and in secure DNS support across Chrome, Edge, and related browsers. The open question is not whether browser support exists. It is how consistent the rollout will be across regions, platforms, and network policies.

For Nexxhost Brief, that is exactly the kind of change worth watching closely. Useful hosting, domain, performance, and website-infrastructure guidance often starts with these small protocol shifts, because they shape how real sites are reached and how real users connect.

Browse: Domains & DNS