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.

HTTPS

Web & applicationIntermediate

Protect HTTP semantics with authenticated TLS.

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

TLS ClientHello

The client offers protocol versions and ALPN; no HTTP body is sent yet.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20TLS ClientHello
1.400198.51.100.20192.0.2.10TLS server flight
2.800192.0.2.10198.51.100.20Finished + encrypted GET
4.200198.51.100.20192.0.2.10Encrypted 200 OK

Protect HTTP semantics with authenticated TLS.

Explain TLS ClientHello and distinguish it from Encrypted 200 OK.

Prerequisites: TCP, TLS, HTTP/1.1

Ready to test your understanding?

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

Learn from the sourceRFC 9110Protocol guide

HTTPS: protocol guide / panduan protokol

Protect HTTP semantics with authenticated TLS.

Lindungi semantik HTTP menggunakan TLS terautentikasi.

Communication walkthrough / Alur komunikasi

  1. TLS ClientHello

    The client offers protocol versions and ALPN; no HTTP body is sent yet.

    Klien menawarkan versi dan ALPN; belum mengirim body HTTP.

  2. TLS server flight

    ServerHello establishes handshake keys; the certificate and Finished are protected.

    ServerHello membentuk kunci handshake; sertifikat dan Finished dilindungi.

  3. Finished + encrypted GET

    After validating identity and Finished, the client sends protected HTTP.

    Setelah memvalidasi identitas dan Finished, klien mengirim HTTP terlindungi.

  4. Encrypted 200 OK

    HTTP fields here are a teaching view, not visible plaintext on the wire.

    Field HTTP di sini tampilan pembelajaran, bukan plaintext yang terlihat di jaringan.

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 9110 ↗