🇮🇹

What Your ISP Actually Sees When You Use Encrypted DNS Alone

David Bombal shows with Wireshark what your ISP actually sees without a VPN, even when you use encrypted DNS, and why DNS encryption alone isn’t enough.

No login, no IP stored.

DISCLOSURE: This article contains affiliate links. If you purchase through these links we may receive a small commission at no additional cost to you. This helps us keep the site free and independent. Our opinions remain unbiased.

The idea that using DNS over HTTPS or DNS over TLS makes you invisible to your ISP has circulated for years. It’s a flawed oversimplification, and David Bombal, a networking and security-focused YouTuber, decided to dismantle it with a practical demonstration: real traffic, a physical tap on Ethernet, and Wireshark open.

The video, published April 17th, runs about thirty minutes and is worth watching if you have the time. It’s only on YouTube, which I won’t embed here, so here’s the link: https://www.youtube.com/watch?v=46hy3r_1VqY so you can open it wherever you prefer.

The Problem: SNI in the ClientHello

Encrypting DNS queries hides requests to the resolver, but it’s not enough to hide the domain name you’re reaching. When your browser starts an HTTPS connection, during the TLS handshake it sends the ClientHello message, which normally contains the SNI field, Server Name Indication, readable by anyone observing the traffic. It tells the server which domain you want to reach, because many different sites can coexist on the same IP address.

Bombal demonstrates it live: even with DNS encryption via Google or Cloudflare, and even with TLS 1.3, visited domains can still appear in plain text in the traffic if the site doesn’t use additional protections. Microsoft, Cisco, Nvidia, ChatGPT: all visible.

ECH: A Partial Solution

Encrypted Client Hello attempts to close this exact gap by encrypting that part of the handshake as well. In Bombal’s packet capture, sites that use it correctly expose only cloudflare-ech.com instead of the real domain. It’s an important step forward, but it doesn’t solve everything: not all sites support it, and even when active, other side-channel clues can remain useful for figuring out where you’re going, starting with the destination IP address.

The Most Practical Solution

In the final section, Bombal activates and repeats the captures: domains are no longer visible on the local network, replaced instead by encrypted WireGuard traffic to the VPN server. In practice, it’s the simplest way to prevent your ISP, corporate networks, or anyone else observing that connection from directly seeing which sites you visit.

The video uses Proton for the demo, but the concept applies to any serious VPN. This doesn’t make you “invisible” in absolute terms though: it simply shifts trust from your Internet provider to your VPN provider, which should be chosen carefully. The key is picking a trustworthy service with a verifiable no-log policy and credible track record. Mullvad is another solid choice here, with a deliberately minimal business model and no accounts tied to user identity. You’ll find an updated list of legitimate VPNs on Le Alternative.

The video is on YouTube and you’ll find it below. If you have ten minutes, jump straight to the Wireshark packet capture section: seeing your own domains scroll past in plain text is more convincing than any written explanation.

Support Yoota · affiliate link

Spread the word

Sniff out what’s new (follow me 🐾)

YOOTA
YOOTA
@en@yoota.it

Sniffing out tech news

502 posts
8 followers

Continua a fiutare

Loading top paws…

Cookies! We don't use tracking cookies or collect personal data, but since this site is federated via ActivityPub ⁂, your visit may connect to Mastodon or other federated servers.Affiliations: Some articles include affiliate links. When you buy through them, we may earn a small commission.