Internet vs. Web: A High School Computer Science Teaching Framework
Share
Students often use network, Internet, Web, Wi-Fi, and website as if they describe the same thing. The fastest way to fix that confusion is not to add more definitions. It is to teach the ideas as layers that solve different problems.
A useful high-school framework is local network → Internet addressing and transport → DNS → Web protocols and documents. Students can then trace what happens when a browser loads a page without collapsing every step into “the Internet.”
Layer 1: a local network moves frames between devices
On a shared network, devices need a way to identify which traffic is meant for them. Ethernet frames use destination MAC addresses so a device can ignore traffic addressed elsewhere. This is a local-network problem, not the whole Internet.
Packet switching also matters here conceptually: data can be broken into packets and routed flexibly instead of reserving one dedicated end-to-end circuit for the entire conversation.
Layer 2: IP gets data to a host; ports get it to an application
An IP address identifies the destination host, but that does not tell the operating system which application should receive the data. Transport-layer port numbers help make that distinction.
This is a good place to correct the idea that an IP address alone is a complete delivery instruction. Ask students: If one computer is running a browser, a game, and a messaging app, how can incoming network traffic reach the right program?
Layer 3: TCP and UDP make different tradeoffs
TCP adds sequence numbers, acknowledgements, retransmissions, and congestion behavior to support reliable ordered delivery. UDP has less overhead and does not provide the same reliability machinery. That does not make UDP useless; real-time applications may prefer lower delay and tolerate occasional missing data.
The key teaching point is that protocol design involves tradeoffs. “More reliable” is not identical to “better for every application.”
Layer 4: DNS translates names to addresses
DNS is not one giant list on one central computer. It is hierarchical and distributed. A browser can begin with a human-readable domain name, and DNS resolution helps find the IP address needed to contact the server.
Cloudflare describes DNS as the Internet’s phonebook: it translates domain names into IP addresses. That analogy is useful as long as students also understand that the system is distributed across many servers rather than stored in one master directory.
Layer 5: the Web is an application that runs on the Internet
This is the distinction students most often need:
- The Internet is the underlying network infrastructure and protocol system that connects networks and moves data.
- The World Wide Web is one application that runs on top of that infrastructure using browsers, web servers, URLs, HTTP, HTML, and related standards.
HTTP handles request/response communication with web servers. HTML is a markup language that describes document structure for browsers to render. HTML does not route packets, and HTTP does not decide how a paragraph should look on the screen.
Walk students through one page load
A concrete “page-load trace” can make the layers visible:
- The user enters a domain name.
- DNS helps resolve that name to an IP address.
- The browser establishes the needed network connection to the destination.
- The browser sends an HTTP request.
- The server sends a response containing resources such as HTML, CSS, and JavaScript.
- The browser interprets those resources and renders the page.
Cloudflare’s explanation of webpage loading uses this same general chain, including DNS, connection setup, HTTP requests and responses, and browser rendering.
A quick misconception check
Give students five terms—IP address, port, DNS, HTTP, HTML—and ask them to match each term to the problem it solves. Then ask one final question: Which of these belongs to the Web specifically, and which support Internet communication more broadly?
This checks understanding better than asking students to memorize five separate definitions.
Optional video companion for YouTube lessons
The free Classroom Video Guide Companion Chrome extension can automatically pause YouTube at question timestamps and display prompts during viewing. It is optional; the lesson materials work normally without it.
Ready-to-use Computer Science resources
- Preview the 10-week curriculum with the free Educator Planning Guide
- Use the Crash Course Computer Science #21–#30 lesson bundle
- View the complete Crash Course Computer Science curriculum