DNS over HTTPS Explained: How It Works and What to Look For
DNS over HTTPS carries DNS messages in HTTPS requests and responses.
Published by Protocol Explorer · Reviewed
How DNS over HTTPS works
A client sends an encoded DNS message to a configured HTTPS endpoint using GET or POST. The server returns a DNS response over the protected HTTP connection.
What to look for in an exchange
The TLS connection protects the DNS message in transit to the chosen resolver. The resolver still sees the query; HTTPS does not make the resolver unaware of it.
Follow an example step by step
- Identify the HTTPS connection to the configured resolver.
- Find the HTTP request method and content type when the HTTPS exchange can be inspected at an endpoint.
- Decode the DNS message carried in the request or response and compare its question and answer.
Common interpretation mistake
Without endpoint access or TLS keys, the DNS message inside HTTPS is not visible in an ordinary packet capture.
Key point to remember
The selected resolver still receives the DNS question; encrypted transport is not the same as anonymity.
Explore the protocol
The DNS over HTTPS overview is free without an account. Its full interactive lesson is included in Protocol Explorer Pro, a one-time $4.99 purchase; an account is required to buy Pro and restore the licence across devices.
Open Protocol Explorer · Compare Free and Pro
Specification
Read the primary specification for DNS over HTTPS for the authoritative protocol details. The interactive scenario is a simplified teaching model, not a capture of your network.
Continue learning
How to read a packet · TCP · UDP · HTTPS