An interactive tour
You type example.com and a page appears.
Here is everything in between.
No single computer knows how to do this. A name gets resolved by a chain of servers that each know only a little. Your data is chopped into packets that take whatever path is open at that millisecond. Layers of protocol wrap and unwrap it. Encryption is negotiated with a stranger you have never met. All of it, usually, in under a quarter of a second.
The whole journey, end to end
Press play and watch one page load. Six distinct conversations happen before a single pixel is drawn — and five of them are with machines you never asked for.
DNS — turning a name into an address
Packets can only be addressed to numbers. example.com means nothing to a
router. Finding the number is a walk down a tree, where every server answers
"I don't know, but ask them."
Routing — there is no wire to the server
Nothing reserves a line for you. Each packet is handed router to router, and every router makes one local decision: which neighbour is closer to that address? Cut a link and watch the network heal.
Packets — envelopes inside envelopes
Every layer treats the layer above it as opaque cargo and staples its own header to the front. Click a header to see what it carries and who reads it.
TCP — reliability on top of a network that loses things
IP promises nothing: packets may vanish, duplicate or arrive out of order. TCP builds an ordered, complete byte stream on top of that mess using nothing but numbering, acknowledgements and patience. Turn up the loss and watch it cope.
TLS — agreeing on a secret in public
Every router on the path can read what passes through it. The padlock means you and the server derived a shared key over that same public path — and that a certificate chain vouches for who the server is.
HTTP — the conversation itself
After all that machinery, the actual request is a few lines of text. But one page is never one request: the HTML arrives first and then tells the browser about everything else it needs.
The cables — the Internet is a physical object
The cloud is glass on the seabed. Latency is not a software setting; it is distance divided by the speed of light in a fibre, and nothing you deploy will beat it.
Putting it back together
The whole stack, in the order it happens, with the words that name each part.