Protocols
Saved & recent

TLS handshake

Also called: TLS negotiation, TLS 1.3 handshake

A TLS handshake agrees on cryptographic parameters, establishes keys, and authenticates the peer or peers required by the chosen mode. In a full TLS 1.3 handshake using certificates, the client and server exchange key shares, the server proves its identity, and Finished messages bind the exchange together.

For example, a browser sends ClientHello and receives ServerHello, followed by encrypted server handshake messages. It validates the server’s credentials before completing its side. This is a simplified certificate-based flow: resumption, client authentication, and a retry request can change the messages, and early data has additional replay considerations.

Read first
TLS
Related
Certificate, ALPN, SNI, 0-RTT early data
Further reading
client server ClientHello + key share ServerHello + key share encrypted handshake server authentication group EncryptedExtensions Certificate CertificateVerify Finished client Finished protected application data simplified full TLS 1.3 handshake server certificate example
Simplified full, certificate-based TLS 1.3 handshake. Server authentication messages and both Finished messages are encrypted after ServerHello. Client certificates, retry, resumption and 0-RTT are omitted.

View in the full Protocols collection