Learn networking from real packets.
Step-by-step walkthroughs of short captures, and plain-language guides to every field you'll see. Free, no account needed.
Learning paths
Not sure where to start? Follow a path: walkthroughs, field guides, and challenges in order. All paths
-
Beginner
Your first packets
What happens when you open a web page: names, connections, and requests, one packet at a time.
-
Beginner
Privacy and the secure web
What encryption hides, what it doesn't, and how to tell when it fails.
-
Beginner
How your home network works
How a device joins the network, finds its neighbours, and reaches the internet.
-
Intermediate
Troubleshooting like a network engineer
Find out why something is slow or broken, and prove whether it's the network.
-
Intermediate
Voice calls on the network
How a call is set up, how the audio travels, and what makes it sound bad.
Answers to network problems
Is it the network, DNS, or the server? Short, direct answers for the problems captures show most, with Wireshark filters. Start with the checklist
- What does "connection refused" look like in a packet capture?
- Why does a connection request get no response?
- What do TCP retransmissions mean?
- Why was my connection reset (TCP RST)?
- Why is a connection slow to open?
- What does NXDOMAIN mean?
- What do SERVFAIL and REFUSED mean in DNS?
- Why does a DNS query get no answer?
Walkthroughs
Each one follows a short capture, one packet at a time. Read it here or open it interactively.
-
Start here
Read Interactive
Loading a web page
DNS, TCP, and HTTP working together to fetch one page.
-
Beginner
Read Interactive
HTTP compared with HTTPS
The same kind of request, readable over HTTP and encrypted over HTTPS.
-
Beginner
Read Interactive
Following a DNS lookup
A name that resolves, a typo that doesn't, and a cached answer.
-
Beginner
Read Interactive
Joining a network
How a device gets an address with DHCP, then makes its first connection.
-
Beginner
Read Interactive
A refused connection
A reachable device that has nothing listening on the requested port.
-
Intermediate
Read Interactive
A failed TLS handshake
A server that can't agree on a TLS version with a modern client.
-
Intermediate
Read Interactive
Tracing the route
How traceroute finds every router between you and a server.
-
Intermediate
Read Interactive
A phone call over the internet
SIP sets up a call, RTP carries the voice, and a few lost packets cost quality.
-
Intermediate
Read Interactive
Home office: checkout failing
A busy home network where one site keeps failing.
Test yourself: packet challenges
Short "find the problem" puzzles, from your first DNS error to a lost packet. A new daily challenge every day.
Protocol field guides
What every field in a packet means and why it matters. The same explanations appear in Learn mode inside an analysis.
- DNS The Domain Name System turns names like example.com into IP addresses.
- TCP TCP carries most of the traffic you care about: web pages, APIs, email.
- TLS TLS is the S in HTTPS.
- HTTP HTTP is how browsers and apps ask for pages and data.
- IPv4 The Internet Protocol puts a source and destination address on every packet so routers can move it across networks.
- IPv6 IPv6 does the same job as IPv4 with far larger addresses, written in hexadecimal like 2001:db8::1.
- UDP UDP sends single messages with no handshake and no delivery guarantee.
- ARP Before a device can send a packet to another device on the same network, it needs that device's hardware (MAC) address.
- Ethernet Ethernet frames carry packets between devices on the same local network, addressed by MAC address.
- ICMP ICMP carries control messages: ping requests and replies, and errors like "destination unreachable" and "time exceeded".
- NTP The Network Time Protocol keeps device clocks accurate.
- DHCP When a phone or laptop joins a network, DHCP gives it an address, the router to use, and DNS servers, in four messages: Discover, Offer, Request, ACK.
- SIP SIP rings the phone.
- RTP RTP carries the actual voice: a small packet every 20 ms in each direction.
- SDP SDP rides inside SIP messages and says where to send the audio and which codecs each side can use.
- QUIC QUIC runs over UDP port 443 and combines the connection and encryption handshakes into one, so pages start faster.
How the health grade works
Every analysis gets a grade from A to F. It comes from fixed rules, not opinion, so the same capture always gets the same grade.
- Four categories. DNS, Connections, Encryption, and Apps & calls. Each finding counts toward one of them. Notes about the capture itself, like seeing only one direction, don't count.
- Each starts at 100. The biggest problem takes off its full weight (critical 60, high 40, warning 20, low 8, note 2); every further one takes off half.
- Plain HTTP costs points. Encryption loses up to 30 points for the share of web connections that weren't encrypted.
- Missing traffic isn't judged. A category with nothing to look at shows a dash instead of a grade.
- The weakest spot matters most. The overall score is half the worst category plus half the average, so one serious problem can't hide behind three healthy ones. A is 90 and up, B 80, C 70, D 60, and anything lower is F.
Try it on your own traffic
Record a capture on your computer, then upload it to see the same explanations for your network.