🛰 TYPE GOOGLE.COM — WATCH THE PACKETS FLY INTERACTIVE · 3D
🔒
DNS · finding the addressTCP · connectingTLS · encryptingHTTP · the page itself
drag to orbit · scroll to zoom · click a machine
STEP 1 / 8URL
🗺 THE 8-STEP JOURNEY OVERVIEW
1
URL — You press Enter
The browser reads what you typed and splits it into pieces: https (how to talk), google.com (who to talk to), and / (which page).
It’s like addressing an envelope — the name and address get read before the letter ever leaves your desk.
2
CACHE — First, check for shortcuts
Your browser asks itself: “Do I already know google.com’s number?” It checks its own memory, then your computer’s.
Like checking your recent calls before reaching for the phone book.
3
DNS — The internet’s phone book
The internet only understands numbers. Your computer asks a DNS resolver: “What number is google.com?” The answer: 142.250.72.14.
You know the name. DNS looks up the phone number.
4
TCP — The handshake: knock, knock
Before real data flows, both sides run a three-message ritual: “Can we talk?” → “Yes, can you hear me?” → “Loud and clear.”
Every phone call starts the same way: “Hello?” — “Hi, can you hear me?” — “Yep!”
5
TLS / HTTPS — Locking the line
Your browser and Google swap keys so everything after this point is scrambled — anyone eavesdropping sees only gibberish. This is when the padlock appears.
Switching from postcards — which anyone can read — to sealed envelopes.
6
HTTP — Finally, asking for the page
Everything so far was setup. Now the actual request goes out over the encrypted line: “GET / — please send me your homepage.”
You’ve dialed, said hello, and agreed on a secret language. Now you finally ask your question.
7
RESPONSE — Google answers
Google’s server replies “200 OK” and streams the page back in many small packets: HTML first, then styles, scripts, and images.
Flat-pack furniture: it doesn’t arrive built. It arrives as numbered parts, plus instructions.
8
RENDER — Your browser builds the page
The browser reads the HTML, applies CSS, runs JavaScript — and paints pixels on your screen. All eight steps? Usually well under a second.
An architect (HTML), a decorator (CSS), and an electrician (JavaScript) — finishing the whole house in the blink of an eye.
📖 KEY TERMS GLOSSARY
URL
The full address you type. It says how to connect, who to talk to, and which page you want.
Cache
A small stash of recently-used answers your browser keeps, so it doesn’t fetch the same thing twice.
IP Address
A device’s phone number on the internet, e.g. 142.250.72.14. Computers only call numbers, never names.
DNS
The Domain Name System — the worldwide service that turns names like google.com into IP addresses.
TCP
Transmission Control Protocol — the rulebook that makes sure packets arrive complete, in order, with nothing missing.
TLS
Transport Layer Security — the encryption layer that puts the S in HTTPS and the padlock in your address bar.
HTTP / GET
The request/response language of the web. GET is the HTTP way of saying “please send me this page.”
Render
Turning code into pixels — layout, colors, text, and images, then painting them on your screen.