TLS 1.3: Handshake, Certificates and Encryption
TLS protects application data between endpoints after a handshake establishes keys. Its security depends on the negotiated parameters and on correct peer identity validation.
Updated · Editorial approach and simulation limits
ClientHello, server response and key agreement
The client starts with ClientHello information such as supported versions, cipher suites, extensions and key shares. The server responds with its selected parameters and key share, then supplies authentication information and completes the handshake. The exact flight depends on the negotiated options and whether the connection resumes prior state.
In TLS 1.3, handshake and application traffic use separate derived secrets. Once the handshake completes, encrypted records carry application data. A packet trace can show record sizes and timing without revealing the protected request.
A certificate is useful only when the client validates it
The server presents a certificate chain that the client checks against its trust store and the requested server name, along with validity and policy checks. A certificate visible in a capture does not prove that validation succeeded, and a certificate issued by a trusted authority does not make the site’s content safe.
When an error occurs, distinguish a trust-chain failure, a name mismatch, expiration, unsupported algorithm or application failure after the handshake. Client diagnostics and certificate verification logs provide evidence that an encrypted network capture alone cannot.
TLS and application protocols
TLS can protect HTTP, email protocols and other application exchanges. ALPN can select an application protocol during the handshake. HTTPS is HTTP over TLS, while HTTP/3 uses QUIC’s TLS integration instead of a TCP-carried TLS session.
TLS protects the channel between its endpoints. A terminating reverse proxy creates one TLS connection from client to proxy and can create another to the upstream; identify those trust boundaries before drawing conclusions from a capture.
Explore TLS interactively
Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.
Specification and source
For exact protocol requirements, consult the primary document: RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3. This page summarizes selected behavior and is not a substitute for the specification.
Related protocol lessons
Browse all security and access protocols · Compare TLS over TCP with QUIC’s integrated handshake