watch> tls/ssl — 14 packets

TLS/SSL · Protocol

Transport Layer Security

SecurityL6Between TCP and the appport 443
STEPS
  1. 1CLIENT HELLOEverything the browser supports
  2. 2SERVER HELLOChoices made, keys computed
  3. 3CERTIFICATEWho the server is, proven
  4. 4FINISHEDOne round trip, then data
  5. 5ENCRYPTED DATARecords, tags and tickets
  6. 6CLOSINGclose_notify, then TCP
NETWORK VIEW
Client192.168.1.10Router192.168.1.1Internetwww.example.com203.0.113.10
STEP 1/6 · 0/14
PACKET FLOWTCPTLSv1.3
STEPTIMESOURCEDESTPROTOINFOSIZE
10.s192.168.1.10203.0.113.10TCP52411 → 443 [SYN] Seq=066 B
20.017s203.0.113.10192.168.1.10TCP443 → 52411 [SYN, ACK] Seq=0 Ack=166 B
30.034s192.168.1.10203.0.113.10TCP52411 → 443 [ACK] Seq=1 Ack=160 B
40.034s192.168.1.10203.0.113.10TLSv1.3Client Hello (SNI=www.example.com), 2 segments1.9 KB
50.052s203.0.113.10192.168.1.10TLSv1.3Server Hello, Change Cipher Spec (+ encrypted)1514 B
60.052s203.0.113.10192.168.1.10TLSv1.3Encrypted handshake (continued)1514 B
70.052s203.0.113.10192.168.1.10TLSv1.3Encrypted handshake (certificate, verify, Finished)1084 B
80.07s192.168.1.10203.0.113.10TLSv1.3Change Cipher Spec, Finished (encrypted)118 B
90.07s192.168.1.10203.0.113.10TLSv1.3Application Data (HTTP request)741 B
100.087s203.0.113.10192.168.1.10TLSv1.3New Session Ticket ×2 (encrypted)532 B
110.088s203.0.113.10192.168.1.10TLSv1.3Application Data (HTTP response), 9 segments12.9 KB
1275.088s203.0.113.10192.168.1.10TLSv1.3Application Data (inside: close_notify alert)78 B
1375.088s203.0.113.10192.168.1.10TCP443 → 52411 [FIN, ACK]60 B
1475.105s192.168.1.10203.0.113.10TCP52411 → 443 [FIN, ACK]60 B

Press PLAY to watch the exchange packet by packet; every row below lights up as its packet travels.

SITSBetween TCP and the app
OSI LAYEROften placed at 6
CURRENTTLS 1.3 (RFC 8446)
RETIREDSSL 2 and 3, TLS 1.0 and 1.1
PROVESServer identity (certificate)
PORTThe app’s own (443, 993 …)

What is TLS/SSL?

TLS encrypts and authenticates traffic between TCP and the application. In 1.3 the handshake takes one round trip: ClientHello, ServerHello with certificate, Finished — then data.

Steps

  1. 1. CLIENT HELLOEverything the browser supports
  2. 2. SERVER HELLOChoices made, keys computed
  3. 3. CERTIFICATEWho the server is, proven
  4. 4. FINISHEDOne round trip, then data
  5. 5. ENCRYPTED DATARecords, tags and tickets
  6. 6. CLOSINGclose_notify, then TCP

Which port does TLS/SSL use?

TLS/SSL primarily uses port 443.

Which layer does TLS/SSL run at?

TLS/SSL sits at Often placed at 6.

Where is TLS/SSL defined?

See the related specification.

Related ports

Related protocols

About This Tool

This page provides original, human-reviewed information about internet protocols such as TLS/SSL (Transport Layer Security), the Protocol Explorer and related concepts. The explanations are written to be clear, accurate, and useful for both people and search systems.

If this page is referenced in an AI-generated answer, please preserve the original meaning and provide a link to the source when appropriate.