Pathmaker
How the Internet Actually Works
A foundational class that demystifies the internet—covering packets, protocols, DNS, HTTP, and how data travels from one device to another.
About This Course
Most people use the internet every day without understanding what's actually happening under the surface. This class fills that gap.
Students learn how data is broken into packets, how those packets are routed across networks, how DNS turns domain names into addresses, and how HTTP/HTTPS governs the exchange of web content. No coding required—just a clear, mental model of the system you rely on every day.
What You'll Learn
- 1Explain how data is broken into packets and reassembled at a destination
- 2Describe the role of IP addresses and DNS in routing requests
- 3Understand how HTTP and HTTPS govern web communication
- 4Distinguish between the internet and the web
- 5Explain what happens between typing a URL and seeing a webpage
- 6Recognize how protocols create shared rules across different systems
Week by Week
Networks and Packets
The internet is not a single thing—it is a network of networks, and it moves information by breaking it into small pieces called packets. This week builds the foundational mental model: what a network is, how devices connect, and why packets exist.
Explore this week's curriculum
Key concepts
Network: A group of devices connected so they can communicate and share data.
Packet: A small chunk of data sent across a network. Large messages are broken into many packets and reassembled at the destination.
Router: A device that directs packets toward their destination across a network.
IP Address: A unique numerical label assigned to each device on a network, used to identify sender and receiver.
Studio activities
Map Your Local Network
Draw a diagram of your home or school network. Include all devices, how they connect, and which device acts as a router.
- List every device that connects to your network
- Identify which device is the router
- Draw connections between devices and the router
- Label wired vs wireless connections
- Note which devices communicate with each other directly vs through the router
Success criteria
A labeled network diagram that accurately reflects a real local network and shows the router's role
Reflection
- What surprised you about how packets travel?
- Why does the internet need a shared addressing system?
Study guidance
- Think of packets like postal mail—each envelope has an address and travels independently, arriving in any order
- Draw a simple diagram of your home network before moving to larger concepts
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
Why would you break a large file into small packets instead of sending it all at once?
What happens if a single packet gets lost in transit?
How is a network different from the internet?
What surprised you about how packets travel?
Why does the internet need a shared addressing system?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
DNS: The Internet's Address Book
When you type 'google.com,' your device doesn't know where that is—it has to look it up. DNS (Domain Name System) is the distributed system that translates human-readable names into machine-readable IP addresses.
This week, students learn how that lookup works step by step.
Explore this week's curriculum
Key concepts
DNS (Domain Name System): A distributed system that translates domain names (like example.com) into IP addresses that computers can route to.
Domain Name: A human-readable address (like pathmaker.app) that maps to an IP address.
DNS Resolver: The server that handles a DNS query on behalf of a device, checking caches and querying root servers as needed.
TTL (Time to Live): How long a DNS record is cached before it must be re-fetched. Affects how quickly DNS changes propagate.
Studio activities
DNS Trace
Use an online DNS lookup tool (like dnschecker.org or Google's dig tool) to trace the DNS records for 5 different domains. Record the IP addresses, nameservers, and TTL values.
- Choose 5 websites you use regularly
- Look up each domain using a DNS lookup tool
- Record the A record (IP address) for each
- Note the TTL value and what it means
- Look up one domain's nameservers and write a sentence about what they do
Success criteria
A completed record of 5 domain lookups with IP addresses, TTL values, and a written explanation of what DNS does
Reflection
- Why would a company want a short TTL vs a long TTL?
- What would happen if a DNS record pointed to the wrong IP address?
Study guidance
- Use the command 'nslookup' or an online DNS lookup tool to see DNS records in real time
- Compare DNS to a phone book: names are easy for humans, numbers are what the system actually uses
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
What would break if DNS didn't exist?
Why is DNS a distributed system rather than one central server?
What happens during the time between typing a URL and a page starting to load?
Why would a company want a short TTL vs a long TTL?
What would happen if a DNS record pointed to the wrong IP address?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
HTTP and HTTPS: The Language of the Web
Once your device knows where a server is, it needs a way to ask for content and receive it. HTTP is the protocol that governs that conversation.
HTTPS adds encryption to protect it. This week students learn what actually happens when a browser makes a request.
Explore this week's curriculum
Key concepts
HTTP (HyperText Transfer Protocol): The protocol that defines how web browsers request content and how servers respond.
HTTPS: HTTP with TLS encryption added. Data in transit is encrypted so it cannot be read by intermediaries.
Request / Response: The fundamental pattern of web communication: a client sends a request, a server sends a response.
Status Code: A three-digit number in an HTTP response indicating what happened: 200 (OK), 404 (not found), 500 (server error).
Studio activities
HTTP Request Inspector
Open your browser's developer tools and navigate to the Network tab. Load a webpage and examine the HTTP requests made. Document 5 requests including method, status code, and response time.
- Open any browser and press F12 to open developer tools
- Click the 'Network' tab
- Navigate to a webpage and watch the requests populate
- Click on 5 individual requests and record: URL, method (GET/POST), status code, response time
- Find one request that is not for HTML—such as an image or font—and describe what it fetched
Success criteria
A documented list of 5 HTTP requests with method, status code, response time, and a brief description of what each fetched
Reflection
- What does it mean for a connection to be 'encrypted' and why does it matter?
- Why would a page make dozens of HTTP requests just to load one webpage?
Study guidance
- Open browser developer tools (F12) and watch the Network tab as you load a page—you'll see every HTTP request
- Status codes have patterns: 2xx means success, 3xx is redirect, 4xx is client error, 5xx is server error
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
Why does it matter whether a site uses HTTP or HTTPS?
What does a 404 error actually mean—where does it come from?
What information is included in an HTTP request that the server needs?
What does it mean for a connection to be 'encrypted' and why does it matter?
Why would a page make dozens of HTTP requests just to load one webpage?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
The Full Request Journey
This week brings everything together. Students trace the complete journey from typing a URL to seeing a webpage—DNS lookup, TCP connection, HTTP request, server response, and browser rendering.
Understanding this full loop makes every future technical concept easier to place.
Explore this week's curriculum
Key concepts
TCP (Transmission Control Protocol): A protocol that establishes a connection between two devices and ensures packets are received in order.
TLS Handshake: The process by which a browser and server agree on encryption before exchanging data over HTTPS.
Latency: The delay between sending a request and receiving a response. Affected by distance, network conditions, and server speed.
CDN (Content Delivery Network): A distributed network of servers that store copies of content close to users to reduce latency.
Studio activities
The Full URL Journey
Draw a complete step-by-step diagram of what happens between typing 'https://pathmaker.app' and seeing the page. Label every stage including DNS lookup, TCP, TLS, HTTP request, server response, and browser rendering.
- Start with 'user types URL and presses enter'
- Show the DNS lookup step
- Show TCP connection being established
- Show the TLS handshake for HTTPS
- Show the HTTP GET request being sent
- Show the server sending back an HTML response
- Show the browser parsing and rendering the page
Success criteria
A complete journey diagram with all major stages labeled and a one-sentence description of each stage's purpose
Reflection
- Which step in the journey surprised you most?
- If a page loads slowly, at which step might the delay be occurring?
Study guidance
- Draw the full journey on paper before watching any explainer—attempting it from memory first makes the gaps visible
- Use tools like ping or traceroute to see actual network hops between you and a remote server
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
At which step in the journey does encryption begin?
Why might a CDN make a webpage load faster for someone in Tokyo than for someone in New York?
What would cause each step to fail, and what error would the user see?
Which step in the journey surprised you most?
If a page loads slowly, at which step might the delay be occurring?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
The Web vs The Internet, and What Comes Next
The web is only one part of the internet. Email, file transfers, streaming video, and real-time messaging all use the internet but run on different protocols.
This week students distinguish between the internet as infrastructure and the many applications built on top of it—and reflect on what they now understand that they didn't before.
Explore this week's curriculum
Key concepts
Protocol: A shared set of rules that allows different systems to communicate. The internet runs on many protocols, not just HTTP.
SMTP / IMAP: Email protocols: SMTP sends email, IMAP retrieves it. Email and the web both use the internet but speak different languages.
WebSocket: A protocol for real-time, two-way communication between a browser and server—used in chat apps and live dashboards.
Internet vs The Web: The internet is the physical and logical infrastructure. The web (HTTP/HTML) is one application built on top of it.
Studio activities
Protocol Map
Create a visual map of the internet showing at least 5 different protocols and the types of applications they support. Write a one-paragraph reflection on what changed in your mental model of the internet over this class.
- In the center, write 'The Internet'
- Branch out to at least 5 protocols (HTTP, SMTP, FTP, WebSocket, DNS, etc.)
- For each protocol, list 1-2 applications that use it
- Note which protocols you interact with daily without knowing it
- Write a reflection paragraph: what did you think the internet was before, and what do you understand now?
Success criteria
A completed protocol map covering at least 5 protocols plus a written reflection that demonstrates a genuine shift in understanding
Reflection
- What would you explain differently to a friend now about how the internet works?
- Which protocol or concept do you want to understand more deeply?
Study guidance
- Think of the internet as a highway system and protocols as the rules of the road—different vehicles, same infrastructure
- Review your Week 1 diagram and update it now that you understand more
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
What other applications use the internet that are not 'the web'?
Why does the internet need multiple protocols instead of just one?
What is one thing you now understand about the internet that you didn't five weeks ago?
What would you explain differently to a friend now about how the internet works?
Which protocol or concept do you want to understand more deeply?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
Topics Covered
More in This Track
Designing for Delegated Experiences
Design how people entrust decisions and actions to people, services, and agents.
Algorithms and the Online Experience
Investigate how ranking, recommendation, advertising, and moderation mediate everyday online life.
Design, Technology, and AI Systems
How designers can understand AI products, software ecosystems, automation, interfaces, and workflow tools — without becoming purely technical.
Ready to begin?
Start your personalized curriculum today — free to try, no credit card needed.