Skip to content
AdminKit

TLS SNI (Server Name Indication)

What is TLS SNI (Server Name Indication)?

Server Name Indication (SNI), defined in RFC 6066, is a TLS extension letting a client state the hostname it wants inside the cleartext ClientHello, so a server hosting multiple HTTPS sites on one IP can pick the right certificate. AdminKit's SSL checker shows which certificate a server actually presents for a hostname.

By AdminKit team, Netbase JSC · Updated

Server Name Indication (SNI) is a TLS extension, defined in RFC 6066 and registered as extension type 0 (server_name) in IANA’s TLS ExtensionType Values registry, that lets a client state which hostname it is trying to reach inside the initial ClientHello message, before the TLS handshake completes. It exists because a server hosting multiple HTTPS sites on one IP address otherwise has no way to know which certificate to present until after the encrypted session is already being negotiated; SNI lets it pick the right one up front, which is what makes shared-IP HTTPS hosting practical at scale — the exact problem Cloudflare’s explainer on SNI describes it solving for servers hosting many HTTPS sites behind one IP. nginx’s guide to configuring HTTPS servers describes SNI the same way, notes that it is mandatory to implement in TLS 1.3, and warns that only domain names can be passed in SNI. Because the ClientHello is sent before encryption is established, a plain SNI value is visible in cleartext to anything observing the connection, revealing which site a client is visiting even though the rest of the session is encrypted — the gap Encrypted Client Hello (ECH), defined in RFC 9849, is designed to close, though deployment still varies widely by browser and server.

AdminKit groups tLS SNI (Server Name Indication) under its machine protocols cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What does TLS SNI let a client do?

State which hostname it is trying to reach inside the initial ClientHello message, before the TLS handshake completes.

Why does SNI matter for shared-IP HTTPS hosting?

It lets a server hosting multiple HTTPS sites on one IP address pick the right certificate up front, instead of having no way to know which one to present.

Is the SNI hostname value encrypted?

No -- because the ClientHello is sent before encryption is established, a plain SNI value is visible in cleartext to anything observing the connection.

What is designed to close the SNI cleartext gap?

Encrypted Client Hello (ECH, RFC 9849), though deployment still varies widely by browser and server.