The complete TLS 1.2 handshake from ClientHello to Finished — certificate exchange, key agreement, and when encryption actually starts, animated step by step.
Scenario
Current step 8/8
HTTP GET /
Application data now flows — over TLS as encrypted records.
Round trips to first byte
3 RTT
TCP 1 + TLS 2 = 3 round trips before the first byte
Numbers above arrows are the step order. In TLS 1.3, parts in {} are already encrypted — the certificate that was plaintext in 1.2 is hidden. Brackets [] mark conditional messages sent only with those cipher suites.
After TCP's 1 RTT, TLS 1.2 needs two more round trips: ClientHello ↔ ServerHello+Certificate, then ClientKeyExchange ↔ Finished — 3 RTT total before the first application byte.
ClientKeyExchange is the crux: the premaster secret encrypted with the server's public key lets both sides derive identical session keys from it plus the hello randoms. Only the server's private key can decrypt it, so eavesdroppers learn nothing.
Its weaknesses: RSA key exchange lacks forward secrecy (a later key leak exposes recorded traffic), and the certificate travels in plaintext. TLS 1.3 fixed both. TCP/TLS Handshake Visualizer