Skip to content

Standard

Server Name Indication

TLS extension carrying the target domain in plaintext, described by the IETF as perhaps the most sensitive unencrypted information in TLS 1.3.

Known aliases

  • server_name extension
  • SNI

Current stories

buildOne report1 publisher

Nine BPF instructions move HTTP instrumentation from the deploy pipeline to the host

A single-file Python agent taps the interface with the same filter tcpdump prints for tcp, and it reconstructs method, path, status and p95 latency for HTTP/1.x while gRPC inside TLS stays an opaque byte count.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+15
Incentives85
Confidence55
buildOne report1 publisher

A fifteen-line listener reads your destination out of TLS without decrypting a byte

A developer dumped the ClientHello that openssl sends and found the requested hostname in plain ASCII inside the server_name extension. A listener holding no private key read it back off the wire, TLS 1.3 included.

Publishers:dev.to

Reality

Evidence70
Adoption30
Hype gap+10
Incentives18
Confidence68
securityConfirmed4 publishers

Android 17 encrypts the handshake field enterprise filters still read

Google's Encrypted Client Hello rollout, wrapped in GREASE decoys so protected sessions look like everything else, removes the plaintext domain that SNI-based logging keys on. Jigsaw reports near-zero interference even in Russia and China.

Perspective Coverage

4 publishers
Builder
Builder 34%
Operator
Operator 55%
Investor
Investor 11%

Reality

Evidence56
Adoption33
Hype gap+16
Incentives74
Confidence63
productOne report1 publisher

Android 17 encrypts the field enterprise web filters read

Google's ECH support hides the destination domain from anything watching the TLS handshake, but only when the app's networking library and the site's CDN both cooperate, so the breakage arrives unevenly.

Publishers:zdnet.com

Reality

Evidence55
Adoption20
Hype gap+25
Incentives62
Confidence55
securityOne report1 publisher

IETF Publishes Encrypted Client Hello as a Standard to Encrypt SNI, With Caveats

RFC 9849 encrypts the ClientHello, so the domain field that SNI allowlists and passive TLS logs depend on stops appearing on the wire. In return, operators inherit a key rotation duty; the spec sets no fixed interval.

Publishers:rfc-editor.org

Reality

Evidence88
Adoption
Not scored
Hype gap−10
Incentives20
Confidence74