What fundamental privacy flaw in standard DNS-over-HTTPS (DoH) does Oblivious DoH (RFC 9230) solve?

Standard DNS-over-HTTPS (DoH, RFC 8484) encrypts DNS traffic against on-path eavesdroppers (ISPs, local Wi-Fi, government censors), but completely centralizes trust in the upstream DoH recursive resolver (such as Cloudflare, Google Public DNS, or Quad9). Because the resolver terminates the TLS connection, it sees BOTH who you are (your client IP address) AND what website you are visiting (the exact domain query). This allows the resolver operator to construct a complete, timestamped browsing profile of every user. Oblivious DoH (ODoH, RFC 9230) decouples client identity from query data using a two-hop cryptographic proxy architecture, mathematically guaranteeing that no single entity knows both the client IP and the query.

How does the Two-Hop Oblivious Architecture (Proxy + Target Resolver) function?

ODoH introduces an independent, untrusted Proxy between the Client and the Target Resolver. The client encrypts its DNS wireformat query using Hybrid Public Key Encryption (HPKE, RFC 9180) directed at the Target Resolver's public key. The client then transmits the encrypted request to the Proxy via HTTP POST. The Proxy terminates the outer TLS connection, sees the client's IP address, but CANNOT decrypt the query payload (seeing only opaque HPKE ciphertext). The Proxy forwards the ciphertext to the Target Resolver. The Target Resolver terminates the outer HTTP connection, sees the Proxy's IP address (NOT the client IP), decrypts the HPKE payload, resolves the DNS query, encrypts the response back to the client, and returns it through the Proxy. As long as the Proxy and Target do not collude, user privacy is absolute.

Why does Oblivious DoH strictly forbid the EDNS Client Subnet (ECS) extension?

EDNS Client Subnet (ECS, RFC 7871) was created to optimize CDN GeoDNS routing by allowing resolvers to append the client's IP subnet (e.g. /24 for IPv4) to authoritative DNS queries. However, appending client subnet information completely defeats the anonymity guarantees of Oblivious DoH, re-exposing user geographic and ISP identity to both the resolver and authoritative nameservers. RFC 9230 strictly mandates that ODoH proxies and target resolvers MUST strip or reject any EDNS Client Subnet options in client queries to prevent geographic de-anonymization.

What is the relationship between Oblivious DoH (RFC 9230), Oblivious HTTP (OHTTP, RFC 9458), and Apple iCloud Private Relay?

ODoH is a specialized DNS application of the broader Oblivious HTTP (OHTTP, RFC 9458) standard published by the IETF in 2024. While ODoH encrypts DNS query messages, OHTTP generalizes the two-hop HPKE proxy architecture for ANY arbitrary HTTP transaction (telemetry reporting, privacy-preserving ads, COVID exposure notifications, and secure telemetry). Apple iCloud Private Relay uses a dual-hop MASQUE/QUIC architecture (Hop 1 run by Apple, Hop 2 run by third-party CDNs like Cloudflare, Fastly, or Akamai) implementing the same cryptographic unlinking principles to ensure Apple knows the user IP but not the destination site, and the destination knows the site but not the user IP.

What latency trade-off does Oblivious DoH incur compared to plaintext DNS and standard DoH?

Plaintext DNS (UDP 53) requires a single network round-trip time (1 RTT, typically 10-25ms). Standard DoH requires an initial TLS 1.3 handshake (1 RTT) followed by an HTTP/2 or HTTP/3 stream exchange (~40-80ms). ODoH adds a second network leg: Client to Proxy (~20-40ms) plus Proxy to Target Resolver (~20-40ms), resulting in an aggregate query latency of ~60-120ms. To minimize latency impact in production, ODoH proxies maintain long-lived, pre-warmed HTTP/2 or HTTP/3 connection pools to target resolvers, amortizing connection establishment over thousands of concurrent client queries.

Verified Specification | Standardized Formulas | Instant Precision

Secure & Private (Zero Data Retention) Free Access • No Sign-Up

Oblivious DNS-over-HTTPS (ODoH) & Oblivious HTTP Architecture Studio

IETF RFC 9230 ODoH & RFC 9458 OHTTP Two-Hop HPKE Dissector, IP Unlinking & Zero-Profiling Simulator

Standard DNS-over-HTTPS (DoH) centralizes trust in upstream recursive resolvers, allowing single entities to build behavioral web dossiers linking Client IPs to visited domains. Oblivious DoH (RFC 9230) and Oblivious HTTP (RFC 9458) decouple client identity from query payload using Hybrid Public Key Encryption (HPKE, RFC 9180) across an independent two-hop relay proxy.

1. Interactive Two-Hop Cryptographic Pipeline Simulator

Inspect what each entity (ISP, Proxy, Target Resolver) can and cannot observe

Target DNS Domain to Resolve

Untrusted Relay Proxy Operator

Target Recursive Resolver (Terminates HPKE)

Privacy & Data Exposure Dissection

Client (You)

IP: 198.51.100.42

Sees IP & Query

→

Relay Proxy

Terminates Outer TLS

Sees Client IP

Zero Query Data

→

Target Resolver

Terminates HPKE Key

Zero Client IP

Sees DNS Query

2. DNS Security & Privacy Protocols Comparison

Evaluate Plaintext DNS vs DoT vs DoH vs ODoH vs Tor Onion routing

DNS Protocol	Transport & Encryption	ISP / Path Visibility	Resolver Profiling Risk	Query Latency	Primary Use Case
Plaintext DNS (RFC 1035)	UDP / Port 53 (Unencrypted)	Full IP + Domain	Full IP + Domain	~10–25 ms (1 RTT)	Legacy networks, local LANs
DNS-over-TLS (DoT) (RFC 7858)	TLS over TCP / Port 853	Encrypted (Port 853)	Full IP + Domain	~40–70 ms	Android Private DNS system default
DNS-over-HTTPS (DoH) (RFC 8484)	HTTP/2 or HTTP/3 / Port 443	Encrypted (Looks like web)	Full IP + Domain	~35–65 ms	Firefox, Chrome, Edge browser defaults
Oblivious DoH (ODoH) (RFC 9230)	Two-Hop HPKE over HTTPS	Zero Visibility	ZERO PROFILING (Unlinked)	~65–110 ms	Maximum consumer privacy, Apple iCloud Relay
Tor DNS Resolution	3-Hop SOCKS5 Onion Circuit	Zero Visibility	Zero Visibility	~400–1,200 ms	High-risk journalism, darknet browsing

3. Production Code Blueprints & Configurations

Go 1.23+ ODoH client, Cloudflare Worker Relay, and DNS HTTPS Resource Records

// Loading blueprint...

Oblivious DNS-over-HTTPS (ODoH) & Oblivious HTTP Architecture Studio

1. Interactive Two-Hop Cryptographic Pipeline Simulator

2. DNS Security & Privacy Protocols Comparison

3. Production Code Blueprints & Configurations

🔍 Companion Workbenches & Verification Tools

Post-Quantum Key Encapsulation: Kyber / ML-KEM & Classic McEliece Studio

HashiCorp Vault & Secrets Architecture Studio

Fully Homomorphic Encryption (FHE) & BFV / CKKS Studio: Zero-Knowledge Compute

Hardware Security Module & PKCS#11 Studio: Cryptoki API, Slots & Non-Extractable Keys

Why Smart Users Are Switching to This Free Toolkit

The Browser Feature Most People Never Use

Stop Paying for Software You Can Get Free

File Conversion Tricks That Save Hours Every Week

This Free Tool Replaced 5 Paid Apps for Our Team

What Your Browser Can Do Without Any Extensions