Encrypted DNS --> Privacy? A Traffic Analysis Perspective
This reveals a critical privacy vulnerability for users relying on encrypted DNS, indicating that current deployments are insufficient against traffic analysis attacks.
The paper tackles the problem of whether encrypted DNS protocols like DoT and DoH protect users from traffic analysis-based monitoring and censorship, showing that traffic analysis can identify domains with high accuracy using 124 times less data than attacks on HTTPS flows, and that DNS-based censorship remains possible despite encryption.
Virtually every connection to an Internet service is preceded by a DNS lookup which is performed without any traffic-level protection, thus enabling manipulation, redirection, surveillance, and censorship. To address these issues, large organizations such as Google and Cloudflare are deploying recently standardized protocols that encrypt DNS traffic between end users and recursive resolvers such as DNS-over-TLS (DoT) and DNS-over-HTTPS (DoH). In this paper, we examine whether encrypting DNS traffic can protect users from traffic analysis-based monitoring and censoring. We propose a novel feature set to perform the attacks, as those used to attack HTTPS or Tor traffic are not suitable for DNS' characteristics. We show that traffic analysis enables the identification of domains with high accuracy in closed and open world settings, using 124 times less data than attacks on HTTPS flows. We find that factors such as location, resolver, platform, or client do mitigate the attacks performance but they are far from completely stopping them. Our results indicate that DNS-based censorship is still possible on encrypted DNS traffic. In fact, we demonstrate that the standardized padding schemes are not effective. Yet, Tor -- which does not effectively mitigate traffic analysis attacks on web traffic -- is a good defense against DoH traffic analysis.