Watch the SYN → SYN-ACK → ACK sequence establish a TCP connection — sequence numbers and SYN_SENT/ESTABLISHED state transitions animated step by step.
Scenario
Current step 4/4
HTTP GET /
Application data now flows — over TLS as encrypted records.
Round trips to first byte
1 RTT
Data can flow right after the single handshake round trip
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.
The 3-way handshake is the minimum round trip needed for a reliable connection: the client sends SYN with its initial sequence number (ISN), the server answers SYN-ACK with its own ISN plus client ISN+1, and the client confirms server ISN+1 with a final ACK.
Three messages are required because both directions need initialization. After SYN-ACK only the client knows the server's ISN — the server can't be sure its message arrived until the third ACK. That's when both sides reach ESTABLISHED.
Sequence numbers anchor each direction's byte stream: ack=101 means 'I have everything up to 100, expecting 101' — the acknowledgment mechanism that carries TCP's retransmission and ordering. TCP/TLS Handshake Visualizer