# DNS over HTTPS explained

URL: https://ekom.blog/dns-over-https-explained/
Published: 2026-11-20
Author: Ekom
Topics: How the internet works

> What DNS over HTTPS (DoH) is, what it hides and what it doesn't, how to turn it on, and why it matters if you run a website or manage a network.

Every time you visit a website, your device first asks a question: "What's the address of this name?" That question is a DNS lookup, and for most of the internet's history it has been sent in plain text.

DNS over HTTPS (DoH) encrypts that question. Here's what that changes and what it doesn't.

## DNS in one minute

DNS is the internet's phone book. You type example.com; your device asks a DNS resolver for the matching IP address; the resolver answers; then your browser connects. If you want the full tour, I covered it in DNS explained for people who just want their site to work and how domain names work, from typing to loading.

The catch: traditional DNS queries travel unencrypted. Anyone on the path can see which names you look up: the café Wi-Fi owner, your internet provider, anyone sitting between you and the resolver. They can't see the page content (HTTPS protects that), but they can see which sites you visit.

## What DoH does

DoH sends DNS queries inside an ordinary encrypted HTTPS connection to a resolver that supports it. To an observer, it looks like normal secure web traffic to that resolver. They can't read which names you're asking about, and they can't easily tamper with the answers.

An analogy: ordinary DNS is shouting your question across a crowded room. DoH is passing a sealed envelope to a clerk. People can see you handed over an envelope, and to whom, but not what's inside.

There's a close cousin called DNS over TLS (DoT), which encrypts DNS on its own dedicated port. Same goal, different packaging. DoH has the advantage of blending in with web traffic.

## What it protects against

- Eavesdropping on public Wi-Fi.

- Tampering: someone rewriting answers to send you to a fake site.

- Casual snooping and logging by networks you don't trust.

## What it doesn't do

This is where the hype goes wrong.

- It doesn't make you anonymous. The resolver you picked still sees your lookups. You've shifted trust from your ISP to that resolver.

- It doesn't hide the sites you visit entirely. After the lookup, your device connects to the destination's IP address, which is visible. And the server name is still visible in parts of the connection unless newer protections are in play.

- It isn't a VPN. A VPN protects all your traffic through a tunnel; DoH only protects DNS. See VPNs explained: how they work.

- It doesn't verify that DNS records are genuine. That's DNSSEC, a separate system.

## The trade-offs

### Privacy vs control

Companies and schools often use DNS to filter malicious or inappropriate sites. If every browser quietly uses its own encrypted resolver, those filters are bypassed. That's why DoH is controversial in managed networks. Parents using DNS-based filtering at home will hit the same problem.

### Centralisation

If everyone uses a few big public resolvers, a lot of lookup data lands in a few places. Pick a provider whose privacy policy you've actually read.

### Local content and speed

Your ISP's resolver is often close by and may return nearby servers for content delivered via CDNs. A distant public resolver can occasionally send you to a slower server. In most cases the difference is small.

## Is it already on?

Quite possibly. Major browsers (Firefox, Chrome, Edge and others) support DoH, and some enable it automatically when your configured resolver supports it, depending on region and settings. Phones and operating systems have their own "private DNS" or "secure DNS" options too.

## How to turn it on

Menu names change, so look for words like "secure DNS", "DNS over HTTPS" or "Private DNS".

- In a browser: open Settings, search for "DNS", and switch on secure DNS. Choose a provider from the list or enter a custom address.

- On Android: look for "Private DNS" in network settings and enter the hostname of a provider that supports it.

- On iPhone, Mac and Windows: recent versions support encrypted DNS settings, either in network settings or through a profile from the provider.

- On a home router: some routers can use encrypted DNS for every device on the network, which is neater than doing it device by device.

After switching, check that websites still load and that any filtering you rely on still works.

## Why it matters if you run a website

DoH is mostly a visitor-side feature, so it doesn't change your DNS records. But it matters in three ways:

- Troubleshooting. "It works for me but not for them" can come down to different resolvers returning different or stale answers after a DNS change. The caching behaviour is described in TTL: why DNS changes take time and DNS propagation: what is really happening.

- Security. Tampered DNS is a real attack route; see domain expiry and DNS hijacking: protecting client domains.

- Network management. If you run an office network, decide whether browsers may use their own resolvers.

## Myths

- "DoH makes browsing private." It makes DNS private from the local network, not from everyone.

- "It slows everything down." Usually the difference is too small to notice.

- "Only criminals need it." Anyone on public Wi-Fi benefits.

## Key takeaways

- DNS lookups are normally unencrypted; DoH wraps them in HTTPS.

- It stops local snooping and tampering, but your chosen resolver still sees the queries.

- It isn't a VPN and doesn't make you anonymous.

- Managed networks and filtering can clash with it.

- Turn it on in your browser or phone, then test that everything works.

## FAQ

### Does DoH replace HTTPS?

No. They protect different steps: DoH covers the lookup, HTTPS covers the page.

### Which provider should I choose?

One whose privacy policy you've read and whose speed you've tested from your location.

## Related reading

- HSTS explained

- What actually happens when you type a web address

- VPNs explained: when you need one and when you do not

Open your browser's settings and search for "secure DNS". Is it already on, and who is the provider?

---

From Ekom (https://ekom.blog/). More: https://ekom.blog/llms.txt
