Encrypted Client Hello (ECH): hiding the site name you connect to

By TechCompare · Updated · How we check

ECH hides the real site name inside an encrypted hello. It only works when the site publishes an ECH key in its DNS HTTPS record, and browsers use it when they can read that record, which usually means secure DNS.

Even over HTTPS, the browser's first message names the site it wants, in a field called Server Name Indication (SNI). Anyone on the network path can read it, so they can see which sites you visit and block some of them. Encrypted Client Hello (ECH), published as RFC 9849 in March 2026, encrypts that first message with a key the site publishes in DNS.

Topic
Encrypted Client Hello
Private site names
Category
HTTPS setup
HSTS, ECH, redirects and compression

How this is calculated

With ECH, the browser sends two hellos in one. The outer one stays readable and names a shared public name, like cloudflare-ech.com for sites on Cloudflare. The inner one, encrypted with the site's ECH key, holds the real name and the rest of the handshake. Someone watching only learns that you connected to that provider.

The key travels in the DNS HTTPS record (RFC 9460) as an ech parameter, as RFC 9848 describes. Keys rotate often, so the record changes too. If the DNS lookup itself goes out in plain text, an observer can still read the name you looked up, so ECH hides much more when DNS is encrypted as well. Firefox turned ECH on by default in version 119 and uses it together with DNS over HTTPS. Chrome turned it on in version 117.

ECH does the most for sites behind a large provider, where the outer name hides one site among many. A site with its own IP address gains less, since the address already gives it away. Cloudflare turns ECH on by default for sites on its free plan, and other plans can switch it on.

The SSL Checker reads the site's HTTPS record from DNS and reports whether it carries an ECH key. It doesn't test the encrypted handshake itself.

Verdict

If your CDN offers ECH, turn it on. Browsers that don't support it simply ignore the key. Check that the HTTPS record shows an ECH key afterward. On your own servers, wait until your web server and TLS library support RFC 9849, and plan for key rotation from the start.

More SSL scenarios

Frequently asked questions

Does ECH hide my visits from my internet provider?
It hides the site name in the TLS handshake. Your provider can still see the IP address you connect to, and the DNS lookup unless that's encrypted too. For a site on a big CDN, the address is shared with many other sites, so ECH plus encrypted DNS hides a lot.
Why does my site have an HTTPS record but no ECH key?
The HTTPS record holds other things too, like the HTTP versions the site offers in alpn and address hints. The ECH key is an optional part that only shows up when the host turns ECH on.
Is ECH the same as ESNI?
ECH replaced it. Encrypted SNI was an earlier draft that only encrypted the site name. ECH encrypts the whole first message, which also hides other fields that could give the site away.