FREE & OPEN
THE OPEN PROTOCOL PLAYGROUND

Make every packet make sense.

Explore the conversations that connect our world. One packet at a time.

66 protocolsZero paywalls. Endless curiosity.

TLS

Security & VPNAdvanced

Observe TLS 1.3 key establishment and server authentication.

SIMULATION01 / 04
Loading topology…
0.0s / 4.2s
01
STEP 1 OF 4Client → Server / peer

ClientHello

The client offers supported versions, cipher suites and an ephemeral key share.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20ClientHello
1.400198.51.100.20192.0.2.10ServerHello
2.800198.51.100.20192.0.2.10Encrypted server flight
4.200192.0.2.10198.51.100.20Client Finished

Observe TLS 1.3 key establishment and server authentication.

Explain ClientHello and distinguish it from Client Finished.

Prerequisites: TCP

Ready to test your understanding?

Rebuild the exchange. Read the fields. Find the mistakes.

Learn from the sourceRFC 8446Protocol guide

TLS: protocol guide / panduan protokol

Observe TLS 1.3 key establishment and server authentication.

Amati pembentukan kunci TLS 1.3 dan autentikasi server.

Communication walkthrough / Alur komunikasi

  1. ClientHello

    The client offers supported versions, cipher suites and an ephemeral key share.

    Klien menawarkan versi, cipher suite, dan key share sementara.

  2. ServerHello

    The server selects parameters; subsequent handshake messages use handshake keys.

    Server memilih parameter; pesan handshake berikutnya memakai kunci handshake.

  3. Encrypted server flight

    EncryptedExtensions, Certificate, CertificateVerify and Finished authenticate the server and transcript.

    EncryptedExtensions, Certificate, CertificateVerify, dan Finished mengautentikasi server serta transcript.

  4. Client Finished

    The client verifies the server identity and transcript before completing the handshake.

    Klien memverifikasi identitas server dan transcript sebelum menyelesaikan handshake.

Source and simulation scope

This is a simplified, deterministic teaching scenario. Timing is illustrative. Messages grouped within one event are explicitly condensed. Hexadecimal fixtures, where shown, contain only the indicated protocol ADU, not a full network capture. No PCAP files are supplied.

RFC 8446 ↗