TLS handshake
What is TLS handshake?
The TLS handshake is the message exchange, compressed to one round trip by TLS 1.3 (RFC 8446), in which a client and server agree a cipher suite, the server proves its identity with a certificate, and both derive session keys. AdminKit's SSL checker reports the negotiated version and cipher suite a live handshake completes with.
By AdminKit team, Netbase JSC · Updated
The TLS handshake is the sequence of messages a client and server exchange before any application data is sent, during which they agree on a protocol version and cipher suite — drawn from the values IANA tracks in its TLS Parameters registry — the server proves its identity with a certificate, and both sides derive the symmetric keys that will actually encrypt the session. TLS 1.3 (RFC 8446) compressed this to a single round trip in the common case: the client’s ClientHello already guesses a key-exchange group and sends key material for it, so the server can reply with its ServerHello, certificate, and a Finished message in one pass, versus the two round trips TLS 1.2 typically needed — Cloudflare’s step-by-step walkthrough of the TLS handshake covers this same one-round-trip-versus-two comparison. MDN’s Transport Layer Security article summarizes what the handshake settles, starting with the TLS version, and notes that TLS 1.3 is the current and most widely used version while TLS 1.1 and 1.0 should no longer be used. Extensions like SNI and ALPN ride inside the same ClientHello/ServerHello exchange, which is why a single handshake can select a certificate for the right hostname and an application protocol like HTTP/2 at the same time the cipher suite and keys are negotiated.
TLS handshake is part of AdminKit’s machine protocols cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What does the TLS handshake accomplish?
It negotiates a cipher suite, lets the server prove its identity with a certificate, and derives the session keys that encrypt the connection, before any application data is sent.
How many round trips does a TLS 1.3 handshake need in the common case?
One, down from the two round trips TLS 1.2 typically needed.
How does TLS 1.3 manage a single-round-trip handshake?
The client's ClientHello already guesses a key-exchange group and sends key material for it, letting the server reply with its ServerHello, certificate and Finished message in one pass.
What extensions ride inside the same ClientHello/ServerHello exchange?
SNI and ALPN, which is why one handshake can select the right certificate and application protocol at the same time it negotiates the cipher suite and keys.