Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
ODoH splits knowledge between two parties: a proxy sees who is asking but not what, and a resolver sees what is asked but not who. Neither can build a profile alone.

What Is Oblivious DNS over HTTPS?
Encrypting DNS solved one problem and created another. With DNS over HTTPS, nobody on the network path can see what a user is looking up — but the resolver can see everything, tied to the client’s address. A user who switches from their internet provider to a large public resolver has not removed the observer; they have changed which company it is. Oblivious DNS over HTTPS, specified in RFC 9230 in June 2022, addresses that by making sure no single party knows both who is asking and what they are asking.
Three parties are involved. The client encrypts the DNS query to the target resolver’s public key using hybrid public key encryption, then sends that opaque blob to an oblivious proxy. The proxy cannot read the query — it has no key — so all it knows is that this client sent something to that target. It forwards the blob to the oblivious target, the resolver, which decrypts it, resolves the name, encrypts the answer, and returns it through the proxy.
The target sees the query but the source address is the proxy’s, not the client’s. The proxy sees the client but only ciphertext. Privacy holds as long as the two do not collude, which is why they must be operated by independent parties — running both yourself defeats the entire design.
Apple’s iCloud Private Relay uses the same separation principle for web traffic, with one provider knowing the user and another knowing the destination. The generalised version of the mechanism, Oblivious HTTP, became RFC 9458 in January 2024.
ODoH removes the ability of a single resolver operator to build a browsing profile linked to an individual. It prevents a proxy operator from learning query content. It leaves everything else exactly as it was.
ODoH is designed for consumer privacy, and for a managed corporate estate it is usually the wrong direction. An organisation needs resolver logs for detection — command-and-control beaconing, newly registered domains, tunnelling, and the earliest indication of most intrusions all appear there. A protocol whose purpose is to ensure nobody can attribute a query to a device removes that telemetry by design.
The practical implications are the same as for ordinary DoH, only sharper. Devices that use ODoH bypass corporate filtering completely and produce no usable log at either the proxy or the target. The response is the same too: configure managed devices to use your own encrypted resolver through Group Policy, Intune, or MDM; disable third-party encrypted DNS in managed browsers; block known proxy and target endpoints at the perimeter; and keep detection that does not depend on DNS, such as flow records and TLS fingerprinting, so that a host talking to an unexpected resolver still stands out.
There are legitimate corporate uses at the margins. An organisation whose research or investigative work would be exposed by its resolver’s query log — legal, journalistic, or competitive intelligence functions — may reasonably want ODoH for a specific isolated group of devices, with that decision documented.
Adoption remains limited. Cloudflare has run ODoH infrastructure since 2020 with partners providing proxies, and support exists in some client libraries, but no mainstream browser or operating system enables it by default. The hard part is not the cryptography; it is sustaining a set of independent proxy operators whose independence is real rather than nominal.
For most UK organisations the useful position is to understand the mechanism, confirm your policy prevents unmanaged encrypted DNS of any kind, and keep DNS telemetry flowing into your SIEM. Our SOC Maturation Services cover building detection that survives this shift rather than depending on protocols that are steadily becoming more private.
With DoH, the resolver sees both your address and your query, so it can build a profile. ODoH inserts a proxy that forwards an encrypted query it cannot read, so the resolver sees the query but not your address, and the proxy sees your address but not the query. Privacy depends on the two parties being genuinely independent.
Only the lookup. After resolving a name you connect to that address, and the connection itself is visible to your network and to anyone observing it. TLS Server Name Indication also reveals the hostname unless Encrypted Client Hello is in use. ODoH removes the resolver’s view of your browsing; it does not make you anonymous on the network.
Generally no. Corporate DNS logs are among the most valuable detection sources available, and ODoH is specifically designed to make queries unattributable. Managed devices should use an encrypted resolver the organisation operates and logs. A narrow exception exists for teams whose research would itself be sensitive, deployed deliberately and documented rather than enabled estate-wide.
Not yet. Cloudflare has operated ODoH infrastructure since 2020 and there are client library implementations, but no major browser or operating system enables it by default. The limiting factor is the need for independent proxy operators whose separation from the resolver is real. Expect gradual growth rather than the rapid adoption DoH saw.
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.