DNS-over-HTTPS: Privacy That Dissolves on Contact
Opaque envelopes. Every letter sealed. A courier who can't read a single word inside. You feel untouchable.
Except the courier weighs each envelope. Logs the timestamps. Counts how often you send. From those three scraps alone, he nails the contents at 95% accuracy.
Not a hypothetical. A working attack against DNS-over-HTTPS in 2025.
In brief: DoH encrypts your DNS queries, yet encrypted packet size and timing betray which sites you visit at 95% accuracy. Encryption and privacy are not the same animal.
Envelopes That Confess
DNS has always been the loudest snitch in the TCP/IP stack. You type a URL, your machine fires a plaintext query to a DNS server over UDP port 53. Your ISP reads it. Your boss reads it. The stranger parked on the same cafe Wi-Fi reads it. Nobody ever gets blamed for eavesdropping because the protocol never bothered with secrecy.
DoH wraps that query in HTTPS and ships it to port 443 so it looks like any other web traffic. Your ISP sees a connection to 1.1.1.1. What you asked for stays hidden.
Solved? Not remotely.
Siby et al. at NDSS 2020 from Epfl published the first landmark finding: DoH is wide open to traffic analysis. DNS traffic looks nothing like regular HTTPS. Shorter bursts, a telltale packet-size spread, a rhythm that screams its own name even through encryption.
DePL at IEEE 2022 pushed the attack into absurd territory. 95% accuracy tagging websites from DoH traffic. Roughly 50 packets suffice against a pool of 10,000 sites. All an attacker needs: packet sizes, timing, direction.
Fifty packets. Loading a single page fires off a dozen DNS lookups for the main domain, CDN, analytics, fonts, trackers. Each website throws off a unique cascade of requests: nytimes.com, then static01.nyt.net, then pnytimes.chartbeat.net, on and on. A fingerprint. Same core idea as identifying someone through mouse movements, applied to DNS instead.
Patched, Repatched, Still Leaking
Knee-jerk fix number one: padding. RFC 8467 says pad packets to standard sizes so all envelopes look alike.
Bushart and Rossow at USENIX FOCI 2020 tested it. Paper title tells everything: Padding Ain't Enough. A 2022 ScienceDirect follow-up drove the spike deeper: even with padding, attack accuracy holds above 95%.
Fix number two: if you can't hide the envelope's shape, hide the sender. ODoH, Oblivious DNS-over-HTTPS. A proxy sits between you and the resolver. Proxy knows who you are, not what you ask. Resolver knows what you ask, not who you are. Clean split.
Elegant on a whiteboard. Hollow in the field.
Salari, Kumar, Rinaudi, Tourani, Sacco, and Esposito published the first scholarly look at ODoH privacy through IEEE DSN in 2025. Fingerprinting still works. A local watcher, your ISP, your employer, your VPN provider, sees the traffic between you and the proxy. Patterns in that traffic are enough to tag websites. Proxies forward envelopes whole, sizes and timing intact. Can't hide what's structurally unhideable.
DNS-over-QUIC? Newer protocol, faster handshakes, sleeker on the wire. Same vulnerability. Studies from IEEE 2025 and Icaiic 2024 found 174 flow features like inter-arrival time, packet count, packet length sufficient for website tagging via transformer models. DoQ inherited the flaw wholesale.
And the killing blow. Say you've encrypted everything: DNS, SNI through ECH, certificates, all of it. Airtight encryption. Hoang et al. at PoPETs 2021 showed that destination IP addresses alone give you away. 84% of 200,000 websites are fingerable from the server IP. Well-known sites: 92%. Well-known sensitive sites: 95%. Encryption means nothing when the address on the envelope is stamped on the outside.
| Protection method | Promise | Attack accuracy |
|---|---|---|
| DoH without padding | DNS encryption | 95%, DePL, IEEE 2022 |
| DoH and RFC 8467 padding | Hide packet sizes | 95%+, ScienceDirect, 2022 |
| ODoH via Oblivious relay | Sender anonymity | Works, IEEE DSN, 2025 |
| DoQ, DNS-over-QUIC | Fast encrypted DNS | Works, IEEE, 2025 |
| Full DoH and ECH | Total encryption | 84-95% via IP, PoPETs, 2021 |
A Duopoly Wearing a Privacy Mask
Nobody brings this up in fingerprinting debates, which is bizarre.
DoH was supposed to spread DNS privacy wide. Reverse happened. Bulk of DoH traffic lands at two addresses: Cloudflare at 1.1.1.1 and Google at 8.8.8.8. With OpenDNS and 114DNS, four providers hold over 90% of open resolvers per Apnic data from 2022. A protocol meant to shield you from ISP snooping handed your browsing history to two megacorps. You swapped one watcher for a richer one. Congratulations.
Gets worse. Using DoH at all is metadata. Your traffic goes to port 443 at 1.1.1.1. ISP can't read the query, can see you're running encrypted DNS. RFC 8467 says it plainly: identifying the traffic as DNS might be trivial. Smaller anonymity set. You stick out.
Corporate setups fare grimmer still. Enterprises run internal DNS for .corp and .local domains. DoH bypasses all of it, shipping internal queries straight to Cloudflare. Breaks internal services and leaks corporate domain names to an outside resolver as a bonus. Firefox kills DoH when it spots enterprise policies, and that toggle is yet another fingerprint. Either you're in the group with DoH on or the group where Firefox shut it off due to enterprise rules. Both groups are smaller than the full pool of internet users.
One more wrinkle. If your IP says Germany and your DNS resolver sits in the US, that's a red flag. DNS and IP geo mismatch is a textbook VPN or proxy tell. WHOX catches this through check C07.
WHOX - We tell real signals from manufactured ones. Check your fingerprint at whox.com and find out what signals leak from your browser and how unique you are.
FAQ
Is DoH altogether useless? No. Shields you from the laziest snooping: a neighbor on your Wi-Fi, a corporate admin without DPI. Against a serious watcher with access to your traffic stream, DoH won't hold.
Which is better: DoH, DoT, or DoQ? For beating traffic analysis, the gap is tiny. All three fall to metadata fingerprinting. DoQ is faster, DoH slips through firewalls better, DoT is simpler to set up. None of them crack the root problem: traffic shape gives away traffic content.
Does Tor fix this? Partly. Tor routes traffic through several nodes and adds noise, making analysis harder, not unworkable. Tor brings its own headaches: speed, compatibility, and exit nodes still seeing your DNS in plaintext unless you layer DoH on top.
What about VPN and DoH together? VPN hides your traffic's destination from your ISP. DoH encrypts DNS inside the tunnel. Sounds solid. Now the VPN provider sees your DoH traffic and can run the same metadata analysis. You didn't kill the watcher. You swapped watchers. Only question is who you trust more: your ISP or a VPN outfit charging $5 a month.
How do I actually protect myself? No perfect answer exists. Stacking VPN and DoH and ECH makes the watcher's job harder, doesn't seal every crack. Each layer raises the cost of attack. None makes it impossible. Only real shield is knowing what data about you is out there. Start with an audit.
Read Next
Related Articles
"Do Not Blow Your Cover": Deconstructing AI Authorship Concealment
Anthropic's Claude Code leaked. We reverse-engineered the concealment architecture: seven interlocking systems from Undercover Mode to anti-distillation, tested against 28 public PRs from Anthropic employees, and mapped every layer the system covers and every one it doesn't.
ResearchThe Randomization Lie: Every Canvas Defense Has Been Defeated
WWW'25 proved it: all 18 extensions and 5 browsers defeated. Canvas noise isn't protection. It's a marker. Zero working defenses.
ResearchThe Entropy Map: Which Browser Signals Give You Away
Skin ridges make every human singular. Browsers carry their own version of that mark, and they're far less coy about handing it over. You never held out your palm. Your browser did it for you, silently, on every HTTP request, to every site, without a whisper of consent.