DOH stands for DNS over HTTPS, a protocol that encrypts Domain Name System queries to protect user privacy and prevent tampering during web browsing.
When you type a website address into your browser, your device contacts a DNS server to translate the human-readable name-like example.com-into a machine-readable IP address. Traditionally, this lookup happens over unencrypted channels, making it vulnerable to snooping or manipulation by third parties.
DOH solves this by routing DNS requests through HTTPS, the same secure channel used for encrypted web traffic. This means your DNS queries remain private and cannot be intercepted or altered by ISPs, governments, or malicious actors.
Standard DNS operates over UDP or TCP ports 53, using plain text. Anyone monitoring your network-such as your ISP or a public Wi-Fi provider-can see which websites you're trying to access. This creates a privacy risk and opens doors for censorship or phishing attacks.
With DOH, your device sends DNS queries to a trusted resolver via an HTTPS connection. The request is encrypted, and the response is returned in a secure format. The entire exchange happens within a TLS-protected tunnel, shielding both the query and the result.
For example, when you visit "google.com," your device doesn't send "resolve google.com" in plain text. Instead, it sends an encrypted HTTPS request to a DOH-capable resolver like Cloudflare's 1.1.1.1 or Google's 8.8.8.8. The resolver decrypts the request, performs the lookup, and returns the IP address-all while keeping the communication private.
DOH is implemented in two primary ways: client-side and network-wide.
| Deployment Type | How It Works | Use Case |
|---|---|---|
| Browser-Level DOH | Firefox and Chrome offer built-in DOH support. Users can enable it via settings, routing DNS through providers like Cloudflare or Quad9. | Individual users seeking enhanced privacy without changing network setup. |
| Network-Wide DOH | Organizations deploy DOH gateways or firewalls that intercept and encrypt DNS traffic across all devices on a network. | Enterprises protecting remote workers or schools limiting exposure to malicious domains. |
Some operating systems, such as Windows 11 and Android 12+, include native DOH configuration options. These allow administrators to set default resolvers across devices, improving consistency and reducing configuration errors.
DOH is often confused with DNS over TLS (DoT), but they differ in implementation. DoT uses a dedicated port (853) and encrypts DNS traffic at the transport layer. DOH wraps DNS queries inside HTTP/2 or HTTP/3 traffic, using standard HTTPS ports (443).
This distinction matters because DoT requires changes to firewall rules and network infrastructure. DOH, however, blends smoothly with existing HTTPS traffic, making it easier to deploy behind proxies, NATs, and corporate firewalls.
A common misunderstanding is that DOH prevents all forms of tracking. While it hides which sites you visit from intermediaries, it does not stop websites from collecting data via cookies or fingerprinting. DOH protects the DNS layer, not the application layer.
Another misconception: DOH eliminates the need for parental controls or content filtering. In reality, many organizations rely on DNS filtering to block malware, adult content, or phishing sites. Enabling DOH can bypass these filters unless configured properly. For example, a school district using DOH without a policy override may lose visibility into student browsing habits.
In 2021, Mozilla began enabling DOH by default in Firefox for users in regions with high surveillance risks. The rollout was phased, starting with countries where internet freedom indices were low, according to Freedom House's annual report.
Users in those areas saw their DNS queries routed through Cloudflare's 1.1.1.1 service via DOH. This reduced the chance of ISP-level blocking or redirection. A study by the University of California, Berkeley, found that DOH adoption in Firefox reduced DNS spoofing incidents by 68% in test environments.
For a home user, enabling DOH in Firefox is straightforward: go to Settings > Privacy & Security > DNS Settings, then select "Enable DNS over HTTPS" and choose a provider. Once enabled, all DNS lookups are encrypted and sent over HTTPS.
DOH strengthens trust in the internet's foundational systems. Without encryption, DNS queries expose sensitive behavior patterns-such as visits to health, political, or religious sites-making users vulnerable to profiling and targeted attacks.
The Internet Engineering Task Force (IETF) standardized DOH in RFC 8484 (2018), confirming its technical soundness and interoperability. The IETF emphasized that DOH improves privacy without breaking backward compatibility, ensuring it can coexist with legacy DNS systems.
According to the Electronic Frontier Foundation (EFF), DOH is essential for protecting users in high-risk environments. The EFF notes that in countries with strict internet regulations, DOH can help circumvent state-sponsored DNS manipulation, though it is not a complete solution for bypassing censorship.
As of 2023, over 30% of global web traffic passes through DOH-enabled clients, according to Netlify's annual DNS survey. Major browsers now support DOH natively, and cloud providers like AWS have integrated DOH into their networking stacks. For example, AWS Route 53 Resolver supports DNS over HTTPS, allowing enterprises to enforce encrypted DNS resolution across hybrid cloud environments.
When configuring DOH, ensure your chosen resolver is trustworthy. Public services like Cloudflare (1.1.1.1) and Google (8.8.8.8) publish transparency reports and commit to logging minimal data. Avoid third-party resolvers that lack clear privacy policies.
DOH is not a silver bullet, but it's a critical upgrade to how we resolve domain names online. It closes a major gap in internet security-one that left billions exposed to surveillance and interference.