The Whole Journey of One Click

Lesson 11 · taught by Pip

You've spent ten lessons learning the parts. This one is the payoff: we follow a single click all the way out and all the way back, so the whole map clicks into place.

Here's the plain idea. When you tap a link, your message doesn't teleport. It travels — through wires, past signposts, into a building, and home again — and every piece you've learned is one leg of that trip.

Think of mailing a letter to a faraway friend and getting a reply the same afternoon. Nothing magic happened; a chain of ordinary helpers each did one small job, quickly, in order.

The trip out

You tap a link to example.com. Your browser needs a number, not a name, so it asks the phone book — DNS — "what's the address for example.com?" Back comes an IP address (Lesson 5).

Now your browser writes its actual request: "Please send me this page." That's HTTP (Lesson 9), and because the link starts with https, the request gets sealed in a locked envelope first — HTTPS — so no one along the way can read or tamper with it (Lesson 10).

That sealed request is too big to send as one lump, so it's chopped into packets — little postcards, each stamped with the destination IP (Lessons 3 and 4). The packets travel as signals down the wire (Lesson 2), and at each junction a router reads the address and forwards them one hop closer (Lesson 6). No single router knows the whole route; each just nudges the postcards onward.

The trip back

The packets arrive at the server (Lesson 8) — the always-on computer that holds example.com. It reassembles your postcards, reads the request, finds the page, and sends it back the same way: chopped into packets, sealed, routed hop by hop, signals down the wire, home to you.

Your browser reassembles the reply, unlocks the envelope, and reads the HTML inside. Then it draws the page on your screen.

The whole round trip — out and back, through a dozen strangers' machines — usually finishes faster than you can lift your finger off the screen.

Why the rules matter

None of this works unless everyone agrees on the rules — the protocols (Lesson 7). DNS, IP, HTTP, HTTPS: they're shared agreements that let machines built by different people, in different countries, cooperate without ever meeting. That's the quiet wonder of the internet. Not one big brain — millions of small, honest helpers following the same playbook.

Your turn

Open a new tab and visit any site, then watch the address bar. Notice the little lock (that's HTTPS) and the name you typed (that's the DNS lookup happening). You can now name what each one is doing — and roughly trace the journey behind it.

You won't know every detail of the net from one course, and that's honest — but you now have the map, and the map is the hard part. 🔦 Ready for the next voyage? Find more at /lighthouse/courses.