Visual RFC.
ALL RFCs / RFC 8484
Read the RFC ↗
RFC 8484 / PROTOCOL MECHANISMS

Understand who can still observe queries

05

HTTPS hides content from some network observers while the DoH service still receives the DNS question.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 8 ↗
RFC 8484 · § 8EXAMPLE
3 / 3
Understand who can still observe queriesHTTPS hides content from some network observers while the DoH service still receives the DNS question.clientDoH resolverread DNS questionTiming / size / endpoint patterns remainEncryption does not eliminate resolver visibility or all linkability
03
Timing and size can still expose patterns to an observer.

Timing and size can still expose patterns to an observer.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Message size, timing, IP addresses, and resolver visibility remain privacy considerations.

  • Message size, timing, IP addresses, and resolver visibility remain privacy considerations.
  • HTTP features such as cookies can add correlation; encryption does not eliminate all linkability.
DETAILS

The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Choose the HTTPS resolver endpoint
  2. Send DNS using GET or POST
  3. Read HTTP and DNS errors separately
  4. Respect DNS TTL and HTTP cache age
  5. Understand who can still observe queries
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗