How the Internet Actually Works
Trace a web request from your keyboard to a server and back, and explain every step that happens in between.
This course is for members
$9 unlocks every course in the library, this one included, plus a credit to build a topic of your own and at least 10 new courses every month.
What you will learn about How the Internet Actually Works
The 7-day sprint
- A Network of Networks. The Internet is not one network but a set of independent networks that agree to forward each other's packets using a common protocol family.
- Packets, Addresses, And Prefixes. IP delivers small, individually addressed, best-effort packets, and every destination is identified by an address that belongs to a numbered block called a prefix.
- DNS, The Distributed Directory. DNS turns names people can remember into addresses machines can route to, using a hierarchy of delegations plus aggressive caching rather than one central list.
- How Routes Are Chosen Between Networks. Independently run networks called autonomous systems exchange reachability information with BGP, and the resulting path is the product of business policy as much as geography.
- TCP, Where Reliability Lives. TCP runs only on the two end hosts and turns a lossy stream of independent packets into an ordered, reliable, rate-controlled byte stream.
- TLS And Why HTTPS Is Trustworthy. TLS wraps a TCP connection in encryption and server authentication so the data survives an attacker who fully controls the network in between.
- The Whole Journey, End To End. Every layer you have learned fires in sequence during a single page load, and knowing the order turns vague network problems into a short list of testable suspects.
The 80/20: the 6 concepts that matter most
- Best-effort packet switching
- The end-to-end principle
- Addresses, prefixes, and the naming hierarchy
- Caching with a time to live
- Interdomain routing as policy
- Connections and the handshakes that start them
The core idea, explained like you are 5
The Internet moves data by cutting it into small independently addressed packets that any network can forward without remembering anything, and pushing all the hard work of making that look reliable out to the two machines at the ends.
Then the quiz and the ladder
10 questions that correct you when you are wrong, and beginner, intermediate, advanced levels, each with a practical exercise.
Created Sep 13, 2026. No mistakes have been reported by learners.
Written from these sources
- RFC 1122: Requirements for Internet Hosts - Communication Layers, rfc-editor.org. day 1 four-layer model and host requirements.
- RFC 1122 - Requirements for Internet Hosts - Communication Layers, datatracker.ietf.org. stateless gateways and end-to-end principle.
- Internet Assigned Numbers Authority (IANA), iana.org. IANA functions, root zone and number coordination.
- What Is IANA? β RIPE Network Coordination Centre, ripe.net. registry allocation to RIRs and DNS hierarchy framing.
- IANA Functions and Related Root Zone Management, ntia.gov. historical IANA function list and why names exist.
- DNS root zone, en.wikipedia.org. PTI, 2016 transition, DNSSEC root signing since 2010.
- Internet Assigned Numbers Authority, en.wikipedia.org. IPv4 and IPv6 allocation block sizes, IPv4 exhaustion.
- Root Zone - ICANNWiki, icannwiki.org. over 1,500 TLDs and ISO 3166-1 ccTLD basis.
- RFC 1034: Domain names - concepts and facilities, rfc-editor.org. day 3 DNS concepts and extensibility.
- RFC 1034 - Domain names - concepts and facilities, datatracker.ietf.org. HOSTS.TXT n-squared motivation and TTL design logic.
- RFC 1034 - Domain Names: Concepts and Facilities | RFCinfo, rfcinfo.com. FQDN anatomy, recursive versus iterative queries.
- RFC 1034 β Domain Names: Concepts and Facilities - Mailer To Go, mailertogo.com. CNAME exclusivity rule and apex domain example.
- RFC 4271 BGP-4, rfc-editor.org. day 4 BGP reachability and AS path.
- RFC 4271 - A Border Gateway Protocol 4 (BGP-4), datatracker.ietf.org. CIDR support and elimination of address classes.
- RFC 4271 - A Border Gateway Protocol 4 (BGP-4) ζ₯ζ¬θͺ訳, tex2e.github.io. classic definition of an autonomous system.
- Border Gateway Protocol (BGP), arubanetworking.hpe.com. path-vector, TCP port 179, peering terminology.
- Using disaggregated route information bases (βRIBSβ) to increase the resiliency of protocols such as the border gateway protocol (βBGPβ), image-ppubs.uspto.gov. speakers advertise only routes they use.
- RFC 4271: A Border Gateway Protocol 4 (BGP-4) | Guide books, dl.acm.org. BGP hijack research and RPKI caution.
- RFC 9293: Transmission Control Protocol (TCP) | RFC Editor, rfc-editor.org. current TCP spec, handshake rationale, obsoleted RFCs.
- RFC 793 - Transmission Control Protocol, datatracker.ietf.org. connection and socket definitions, historical context.
- New TCP standard, RFC 9293, afnic.fr. congestion algorithms and reordering repair.
- Evaluating the Stream Control Transmission Protocol Using Uppaal, arxiv.org. TCP state machine details for day 5.
- Verification and Attack Synthesis for Network Protocols, arxiv.org. half-open connections treated as anomalous.
- RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3 | RFC Editor, rfc-editor.org. day 6 TLS 1.3 goals, AEAD, 0-RTT caveat.
- Layered Performance Analysis of TLS 1.3 Handshakes: Classical, Hybrid, and Pure Post-Quantum Key Exchange, arxiv.org. 1-RTT handshake and connection latency budget.
- TLS (Transport Layer Security) Explained: Why TLS 1.3 is the New Standard, securew2.com. TLS 1.3 scope and removed RSA key transport.
- TLS 1.3 is finally published by the IETF as RFC 8446 - Hashed Out, thesslstore.com. older TLS versions needing two round trips.
- A Brief History of the Internet - Internet Society, internetsociety.org. NCP limits and the 1983 TCP/IP transition.
- New Year's Day Marks 30th Anniversary of Major Milestone for Global Internet - Internet Society, internetsociety.org. 1 January 1983 cutover date.
- Final report on TCP/IP migration in 1983 - Internet Society, internetsociety.org. IMP 8-bit addressing, 50 Kb/s links, 1982 DoD plan.
- Milestone-Proposal:Transmission Control Protocol (TCP) and the Architecture of the Internet, 1974 - IEEE Milestones Wiki, ieeemilestones.ethw.org. Kahn 1972, Cerf 1973, months of coexistence.
- History of the Internet β Information, People, and Technology, psu.pb.unizin.org. flag day framing and early packet switching history.