Encrypted Client Hello (ECH / ESNI)
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://tldfyi.com/iframe/glossary/encrypted-sni/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>
Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://tldfyi.com/glossary/encrypted-sni/
Add a dynamic SVG badge to your README or docs.
[](https://tldfyi.com/glossary/encrypted-sni/)
Use the native HTML custom element.
Encrypted Client Hello (ECH), formerly known as Encrypted SNI (ESNI), is a TLS extension that encrypts the Server Name Indication (SNI) field in a TLS handshake. The SNI field traditionally reveals which domain a client is connecting to even when the traffic itself is encrypted. ECH closes this privacy gap by using a public key published in the domain's [[dns|DNS]] (as an HTTPS or SVCB record) to encrypt the SNI, preventing ISPs and network observers from knowing which specific hostname on a shared IP is being visited. ECH requires [[dns-privacy|DNS privacy]] (e.g., [[dns-over-https-browser|DoH]]) to be fully effective.
Example
Without ECH, a passive observer on a CDN-hosted IP sees 'TLS ClientHello → target: example.com' even over HTTPS. With ECH, the SNI field is encrypted, revealing only the CDN's outer hostname.