Learn
LoginRegister
FundamentalsBeginnerFree lab

Fundamentals · browser room

HTTPS / TLS Handshake

Beginner80 ptsTLSHTTPS

Objective

ClientHello → cert → keys → encrypted HTTP.

Cyber Flow Explorer · 4 steps · Network / Sequence / Packet / Code.

Isolated browser lab. Practice here first — no live targets. Optional deeper practice lives in the Academy library after you finish this room.

Answer panel

Challenge workspace

Complete the room tasks, then submit here to mark the room done.

CYNARKS

Teaching simulation · not live capture

HTTPS / TLS Handshake

Do not intercept production TLS without authorization.

Real world · Banking apps, Learn portals, and admin desks all rely on TLS so passwords and session cookies are never cleartext on the wire.

Attack · MITM only works if the client accepts a forged cert (user click-through or compromised CA).

Defense · Valid cert chains, HSTS, and certificate pinning (where appropriate) close the MITM path.

  • Control · TLS 1.2+ only; prefer TLS 1.3
  • Control · HSTS + modern cipher suites
  • Control · Monitor for unexpected certificate issuers

1. TCP

Browser

SNI
TCP

:443 up

HTTPS :443

lab.local
TCP is already ESTABLISHED on port 443.

:443 up

  • #1 client → server TCP :443 up

Space · ← → · R restart

Hint

TLS encrypts application bytes.

Why this is correct

HTTPS = HTTP inside TLS after handshake.