CyberKit

SNI Inspection

Also called Server Name Indication, ESNI, Encrypted Client Hello.

Reading the destination hostname from the TLS handshake.

What it is

Server Name Indication is a TLS extension that carries the requested hostname in cleartext during the handshake so a server can present the right certificate. Inspecting it reveals where an encrypted session is headed without breaking the encryption.

Why it matters

SNI is one of the few plaintext signals left in TLS, valuable for spotting connections to suspicious domains. Encrypted Client Hello aims to hide it too, shifting visibility back to IP and fingerprint data.

In practice

Discovering a connection's SNI named a freshly registered domain, prompting the analyst to treat the otherwise opaque session as suspect.

What to look for

  • Hostnames in TLS client hellos.
  • Mismatches between SNI and the certificate presented.
  • Missing SNI where you expect it.

Common mistake

Relying on it long term. Encrypted Client Hello hides SNI.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Wireshark Open source

    Opens a capture packet by packet so you can see exactly what crossed the wire. Our notes.

  • Zeek Open source

    Turns traffic into structured logs for connections, DNS, HTTP, TLS and more. Our notes.

  • Suricata Open source

    An IDS that alerts on known patterns and logs protocol metadata alongside. Our notes.

  • Arkime Open source

    Indexes full packet capture at scale so you can search and pull sessions later. Our notes.

Read next

Sources