Lesson Plan

• Describe the sequence of processes that occur when a user enters a URL, from parsing to rendering.
• Explain the role of DNS in translating domain names to IP addresses.
• Illustrate how TCP/IP and (optional) TLS establish a connection for HTTP/HTTPS requests.
• Analyse an HTTP request and response, identifying key components and status codes.
• Evaluate how the browser renders HTML, CSS, and JavaScript to display a web page.

• Projector and screen
• Whiteboard and markers
• Printed flow‑chart handouts of the URL‑to‑page process
• Computers with internet access and a web browser
• Network‑step cards for group activity
• Worksheet for DNS lookup and HTTP request analysis

Have you ever wondered how typing a web address instantly brings up a page? Review what a URL looks like and recall that browsers retrieve information from servers. Today you will be able to trace each step from entering a URL to seeing the page displayed, and you will know how to check each part of the process.

1. Do‑Now (5’) – Students write what they think happens after entering a URL and share ideas.
2. Mini‑lecture (10’) – Present the six‑step process with a flowchart, emphasizing URL parsing and DNS lookup.
3. Interactive demo (15’) – Live browser demonstration showing a DNS lookup (nslookup) and inspecting network requests in DevTools; students note each step.
4. Group activity (15’) – Teams arrange shuffled step cards into the correct sequence and add brief timing notes.
5. Consolidation quiz (10’) – Quick Kahoot/exit quiz covering protocols, ports, and status codes.
6. Reflection (5’) – Discuss common errors (e.g., 404, DNS failure) and how browsers handle them.

We reviewed the full journey of a web page from URL entry to rendering on the screen. For the exit ticket, write three key actions the browser performs during this process. For homework, research a security protocol such as HTTPS/TLS and prepare a short summary of how it protects web traffic.