Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
DoH carries name lookups inside ordinary HTTPS traffic on port 443. It protects users on hostile networks and removes a detection source from enterprise defenders.

What Is DNS over HTTPS?
Classic DNS travels in plaintext over UDP port 53. Anyone on the path — a coffee shop router, an internet provider, a state-operated middlebox — can read every name a device looks up and can forge replies. DNS over HTTPS, specified in RFC 8484 in October 2018, wraps the same queries in an HTTPS request to a resolver endpoint, usually a POST or GET to a URL such as https://dns.example/dns-query carrying a application/dns-message body. The queries become confidential and authenticated, and they become indistinguishable from any other web traffic.
The design decision that generated the controversy was reusing HTTPS rather than defining a dedicated port. DNS over TLS encrypts the same traffic on port 853, where a network operator can see it, allow it, or block it as a category. DoH is mixed in with everything else on 443, so blocking it means blocking specific destinations rather than a protocol.
For a user on a censored or hostile network that is the entire point. For an enterprise, it means an endpoint can quietly stop using the corporate resolver and the security team loses one of its best telemetry sources without noticing. The debate was sharp enough in the UK that the Internet Services Providers’ Association nominated Mozilla as an “internet villain” in July 2019 over its DoH plans, a nomination later withdrawn after considerable criticism.
Firefox enables DoH by default for users in the United States and offers it elsewhere, with Cloudflare, NextDNS, and others as providers. Before switching, it queries the canary domain use-application-dns.net; if the network returns NXDOMAIN, Firefox leaves DoH off. That is the supported way for an organisation to signal that its own resolution should be used.
Chrome and Edge take a different approach called automatic upgrade: if the system resolver already in use publishes a known DoH endpoint, the browser upgrades to the encrypted version of the same provider. Resolution destination does not change, so corporate filtering continues to apply. Windows 11 and recent Android and iOS releases support encrypted DNS at the operating system level, which is the preferable place to configure it.
DNS logs are one of the highest-value detection sources available: command-and-control beaconing, newly registered domains, tunnelling, and the earliest stage of most intrusions all appear there. When a device bypasses the corporate resolver, those logs go dark for that device. Malware authors noticed quickly; families including Godlua and several commodity loaders have used DoH for resolution precisely to avoid inspection.
Equally, some of the objection is overstated. DoH does not hide which servers a host connects to, because the subsequent TCP or QUIC session still goes somewhere observable. It hides the lookup, not the conversation. And the alternative is not a secure baseline — it is plaintext DNS that an attacker on the same network can forge.
The workable position is to run encrypted DNS yourself rather than to fight it.
DnsOverHttpsMode policy in Chrome and Edge and the equivalent Firefox enterprise policy.For UK public sector organisations, the NCSC’s Protective DNS service supports encrypted transport, so filtering and encryption are not in conflict. The goal is encrypted DNS to a resolver you control and log — not plaintext, and not a resolver chosen by the browser vendor. Our SOC Maturation Services include building DNS telemetry that survives this transition.
Both encrypt DNS with TLS. DoT uses dedicated port 853, so network operators can identify, permit, or block it as a protocol. DoH carries queries inside ordinary HTTPS on port 443, mixed with all other web traffic, which makes it very hard to block selectively. The cryptography is comparable; the operational difference is visibility and control.
Only partially. You can block known public DoH endpoints by address or hostname, disable it through browser policy on managed devices, and return NXDOMAIN for the Firefox canary domain. None of this stops an unmanaged device using an endpoint you have not listed. The durable approach is providing your own encrypted resolver and enforcing its use on managed endpoints.
It does when the endpoint resolves through a third-party provider, because your filtering and logging never see the query. It does not when the device uses your own resolver over an encrypted transport, which is the recommended configuration. Chrome and Edge automatic upgrade preserves filtering because it keeps the same resolver and only encrypts the connection.
Both, depending on the context. For an individual on an untrusted network it prevents eavesdropping and forged responses, which is a clear gain. For a defender it removes a valuable detection source if devices bypass corporate resolution, and malware has adopted it for the same reason. The resolution is encrypted DNS to a resolver the organisation operates and logs.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.