PROTOCOL EXPLORERLearn how the internet works
Now learningHTTP · Web communicationOverview · 5 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

HTTP

Active

Hypertext Transfer Protocol

HTTP defines the messages exchanged by a browser and a web server. A client requests a resource, and the server returns a status, headers and often a body. In HTTP/1.1 the start line and headers are readable text; the body can carry HTML, images or other media.

Layer
Application (Layer 7)
Default port
80 (HTTPS: 443)
Transport
TCP
Data format
Text · headers + optional body
Common methods
GET, POST, PUT, DELETE, HEAD
Defined in
RFC 9110, RFC 9112
Read the complete guide ↗

Packet flow

DNSTCPRequestResponse
No.TimeSourceDestinationProtocolInfoSize
10.000s192.168.1.108.8.8.8DNSStandard query A www.example.com75 B
20.012s8.8.8.8192.168.1.10DNSStandard query response A 203.0.113.1091 B
30.024s192.168.1.10203.0.113.10TCP52344 → 80 [SYN] Seq=066 B
40.041s203.0.113.10192.168.1.10TCP80 → 52344 [SYN, ACK] Seq=0 Ack=166 B
50.058s192.168.1.10203.0.113.10TCP52344 → 80 [ACK] Seq=1 Ack=160 B
60.058s192.168.1.10203.0.113.10HTTPGET / HTTP/1.1114 B
70.076s203.0.113.10192.168.1.10HTTPHTTP/1.1 200 OK (text/html)132 B

Learn Internet Protocols, Packet by Packet

Learn 14 internet protocols through packet animations, sequence diagrams and a byte inspector. Explore free labs for DNS, TCP, UDP, HTTP, TLS and more.

A PRACTICAL LEARNING PATH

From the first lookup to an encrypted page

Start with IP addressing, compare TCP and UDP, then follow DNS, HTTP and TLS. Continue with network configuration, diagnostics, email, file transfer and remote access. Every guide includes a step-by-step explanation, a common misconception and a local packet lab.

APPLICATION

How HTTP Works: Requests and Responses

Trace an HTTP/1.1 GET request and 200 OK response. Inspect the request line, headers and HTML body in an interactive packet lab.

5 lessons · open guide →
SECURITY

How HTTPS Works: TLS and Encrypted HTTP

Follow an HTTPS connection through DNS, TCP and TLS 1.3. Compare visible handshake fields with the encrypted HTTP request and response.

6 lessons · open guide →
CORE

TCP Handshake and Retransmission

Animate the TCP three-way handshake and see how sequence numbers, acknowledgements and retransmission recover a lost segment.

5 lessons · open guide →
CORE

UDP Explained: Datagram Loss and Reordering

Watch UDP datagrams arrive out of order, lose one in flight and receive application echoes. Compare raw arrival order with app-side reordering.

5 lessons · open guide →
CORE

IPv4 Routing, TTL and Path MTU

Compare an IPv4 packet before and after a router forwards it. Inspect its next hop, TTL, link-layer addresses and path MTU error.

4 lessons · open guide →
APPLICATION

How DNS Resolution Works

Follow a recursive DNS lookup from resolver to root, .com and authoritative servers. Inspect A records, referrals, flags and cache TTL.

5 lessons · open guide →
APPLICATION

DHCP Discover, Offer, Request and Acknowledge

Watch a client obtain an IPv4 lease through DHCP Discover, Offer, Request and Acknowledge. Inspect broadcast traffic and configuration options.

4 lessons · open guide →
CORE

ICMP Echo, Ping and Time Exceeded

Compare ICMP echo request, echo reply and Time Exceeded packets. See how ping identifies replies and how a router reports an expired TTL.

4 lessons · open guide →
APPLICATION

How SMTP Sends Email

Trace an SMTP conversation from EHLO and STARTTLS through MAIL FROM, RCPT TO and DATA. Learn how envelope addresses differ from message headers.

5 lessons · open guide →
APPLICATION

How POP3 Retrieves Email

Inspect a POP3 session using STAT, RETR, DELE and QUIT. See when messages are downloaded and when pending deletions take effect.

4 lessons · open guide →
APPLICATION

How IMAP Syncs Mailboxes and Flags

Follow IMAP SELECT, UID FETCH and UID STORE in a mailbox session. See how a client fetches headers and updates the server’s read flag.

5 lessons · open guide →
APPLICATION

FTP Control and Passive Data Connections

Follow FTP commands on the control connection and see how EPSV opens a separate passive data connection to transfer a file.

5 lessons · open guide →
SECURITY

How SSH Works: Host Keys and Secure Channels

Follow SSH version exchange, key negotiation, host verification and user authentication. See how an encrypted session opens its first channel.

5 lessons · open guide →
SECURITY

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.

5 lessons · open guide →

Check your understanding

What does a 404 response mean?

Try the workbench

Reading definitions is easier when you can connect them to a packet. Each guide pairs explanations with a visual lab, byte inspection and a short knowledge check.

  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.

Standards and scope

Original NavSprout implementation, informed by IETF protocol standards. The lab focuses on IPv4, HTTP/1.1 and a conceptual TLS 1.3 flow. It is a teaching simulation, not a complete network stack.

TCP · RFC 9293 · HTTP · RFC 9110 · TLS · RFC 8446