NavSproutNavSprout / A home for good tools✳
Submit

INTERACTIVE LEARNING TOOL

Protocol Explorer · HTTPS

Explore internet protocols with animated messages, real arrival order and packet inspection.

Read the learning guides ↓
PROTOCOL EXPLORERLearn how the internet works
Now learningHTTPS · Secure web communicationOverview · 6 steps
Learning progress0%
0 / 14 complete · 0 in progress
Client192.168.1.10Router192.168.1.1InternetDNS Resolver8.8.8.8Web Server203.0.113.10

Protocol overview

HTTPS

Active

HTTP over TLS

See how a browser combines HTTP semantics with authenticated encryption. HTTPS protects the exchange between TLS endpoints, including paths, headers and bodies.

Layer
Security over transport
Default port
443
Transport
TCP + TLS (this lab)
Data format
HTTP inside encrypted TLS records
Defined in
RFC 9110, RFC 8446
Read the complete guide ↗

Packet flow

DNSTCPRequestResponse
No.TimeSourceDestinationProtocolInfoSize
10.000s192.168.1.108.8.8.8DNSStandard query A www.example.com75 B
20.024s8.8.8.8192.168.1.10DNSStandard query response A 203.0.113.1091 B
30.048s192.168.1.10203.0.113.10TCP52344 → 443 [SYN] Seq=066 B
40.072s203.0.113.10192.168.1.10TCP443 → 52344 [SYN, ACK] Seq=0 Ack=166 B
50.096s192.168.1.10203.0.113.10TCP52344 → 443 [ACK] Seq=1 Ack=160 B
60.120s192.168.1.10203.0.113.10TLSClientHello · supported_versions=TLS 1.3113 B
70.144s203.0.113.10192.168.1.10TLSServerHello · TLS_AES_128_GCM_SHA256109 B
80.168s203.0.113.10192.168.1.10TLSEncrypted handshake · illustrative ciphertext107 B
90.192s192.168.1.10203.0.113.10TLSClient Finished · illustrative ciphertext107 B
100.216s192.168.1.10203.0.113.10TLSApplication data · illustrative ciphertext107 B
110.240s203.0.113.10192.168.1.10TLSEncrypted HTTP response107 B

NAVSPROUT · PROTOCOL FIELD GUIDES

HTTPS, packet by packet.

See how a browser combines HTTP semantics with authenticated encryption. HTTPS protects the exchange between TLS endpoints, including paths, headers and bodies.

PROTOCOL FIELD GUIDE

How HTTPS works

See how a browser combines HTTP semantics with authenticated encryption. HTTPS protects the exchange between TLS endpoints, including paths, headers and bodies.

Default port
443
Transport / carrier
TCP + TLS (this lab)
Category
security

1. Prepare a secure request

The browser reads the HTTPS URL and selects authenticated encryption before sending HTTP.

2. Find the destination

DNS supplies the address. Traditional DNS and IP routing can still reveal destination information even when the HTTP exchange is encrypted.

3. Connect with TCP

For HTTPS over TCP, a transport connection comes first. HTTP/3 follows a different path using QUIC.

4. Negotiate TLS

ClientHello and ServerHello negotiate parameters and key shares. TLS 1.3 encrypts subsequent handshake messages after ServerHello.

5. Send encrypted HTTP

HTTP request and response bytes travel inside authenticated TLS records. A passive observer sees record lengths and timing, not plaintext HTTP.

6. Render a secure page

The browser decrypts and authenticates the response, parses HTML and displays the page. A secure connection authenticates the hostname, not the claims on the page.

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

Check your understanding

What is hidden inside HTTPS records?

Why it’s hereNAVSPROUT ORIGINAL

Reading definitions is easier when you can connect them to a packet. This first-party learning tool pairs static explanations with a visual lab, byte inspection and a short knowledge check. All course data and application resources ship with NavSprout.

  1. Choose DNS and follow the lookup from client to authoritative server.
  2. Switch to the sequence view, then inspect a packet and select a field to highlight its bytes.
  3. Compare TCP with UDP, answer the quiz and export your progress.

Frequently asked questions

What happens when I open a website?

A typical first HTTPS visit can involve DNS resolution, a transport connection, a TLS handshake and an HTTP exchange. Caches, connection reuse and HTTP/3 can change this sequence.

How are TCP and UDP different?

TCP presents a reliable ordered byte stream. UDP preserves individual datagram boundaries without built-in delivery guarantees. Applications choose the behavior they need.

Are these real captured packets?

No. Frames are generated locally for teaching. Header lengths and checksums are calculated, while TLS ciphertext and some negotiation payloads are illustrative. Downloaded PCAP files contain synthetic examples, not live traffic.

Can I learn without JavaScript or an account?

All 14 protocol guides and their lesson explanations are available as ordinary HTML without signing in. JavaScript powers animations, byte inspection, local progress and quizzes.

Where is my progress saved?

Only in this browser’s local storage. Export a progress JSON file to move it to another device. Clearing browser data can remove progress.

MAKE A THOUGHTFUL CHOICE

Your shortlist, side by side.

Pricing models are indicative. Check each official website for current plans and limits.