PROTOCOL EXPLORERLearn how the internet works
Now learningTLS / SSL · Encrypted transportOverview · 5 steps
Learning progress0%
0 / 14 complete · 0 in progress
Client192.168.1.10Router192.168.1.1InternetWeb Server203.0.113.10

Protocol overview

TLS / SSL

Active

Transport Layer Security

Understand the TLS 1.3 handshake: key agreement, server authentication, transcript verification and encrypted records. SSL is a legacy name, not the protocol used in this lesson.

Layer
Security over transport
Default port
Application dependent
Transport
Usually TCP; TLS 1.3 shown
Data format
Handshake messages + protected records
Defined in
RFC 8446
Read the complete guide ↗

Packet flow

DNSTCPRequestResponse
No.TimeSourceDestinationProtocolInfoSize
10.000s192.168.1.10203.0.113.10TLSClientHello · supported_versions=TLS 1.3113 B
20.024s203.0.113.10192.168.1.10TLSServerHello · TLS_AES_128_GCM_SHA256109 B
30.048s203.0.113.10192.168.1.10TLSEncrypted handshake · illustrative ciphertext107 B
40.072s192.168.1.10203.0.113.10TLSClient Finished · illustrative ciphertext107 B
50.096s192.168.1.10203.0.113.10TLSApplication data · illustrative ciphertext107 B

TLS 1.3 Handshake Explained

Explore ClientHello, ServerHello, encrypted handshake messages and Finished. See which TLS 1.3 fields are visible and when traffic becomes encrypted.

Understanding TLS / SSL

Understand the TLS 1.3 handshake: key agreement, server authentication, transcript verification and encrypted records. SSL is a legacy name, not the protocol used in this lesson.

Default port
Application dependent
Transport / carrier
Usually TCP; TLS 1.3 shown
Category
security

What to look for in the lab

Find the offered version in ClientHello and the selected cipher suite in ServerHello. Then inspect the next record. TLS 1.3 encrypts handshake messages after ServerHello, so the lab explains the protected contents alongside illustrative ciphertext.

1. Offer a ClientHello

The client offers supported versions, cipher suites and a key share. A TLS 1.3 ClientHello still contains legacy compatibility fields.

2. Select a ServerHello

The server chooses compatible parameters and its key share. Both endpoints derive handshake traffic secrets from the shared key exchange and transcript.

3. Authenticate the server

EncryptedExtensions, Certificate and CertificateVerify follow under handshake encryption. The certificate binds an identity to a public key; a signature proves possession.

4. Verify Finished

Finished authenticates the transcript with derived keys. The client validates the server and sends its own Finished before ordinary application data.

5. Protect application records

AEAD encryption authenticates and encrypts each record. TLS 1.3 encrypted records have an outer application_data type even when they carry handshake content.

Protocol relationships

Protocols cooperate across layers. Compare the neighboring lessons to distinguish addressing, delivery, application semantics and encryption.

Standards and editorial method

Written and implemented independently by NavSprout. Lessons summarize public protocol standards using synthetic documentation addresses and fictional credentials. Consult the standards for complete wire formats and normative behavior.

RFC 8446 ↗

Check your understanding

What does Finished verify?