Open a reliable path.
Packets may take different physical routes, but the transport layer presents an ordered conversation.
ONE URL · MANY SYSTEMS
How does the internet
find a website?
You type a human name. In less than a blink, machines find a numbered address, build a secure connection, ask for files, and paint pixels.
Edit the address, then send it through the network.
01One request,
THE JOURNEY
One request,
six handoffs.
TRY A SHORTCUT
Use cached DNS?
If your device already knows the address, it can skip the directory lookup.
STEP 01 · BROWSER
Turn a name into a destination.
The browser parses the URL, checks local caches, and asks for the IP address associated with the domain.
regardedexplanations.com → ?
02
THE DIRECTORY
DNS is not one giant phonebook.
It is a distributed chain of “ask someone more specific.”
YOUR HELPFUL MIDDLEMAN
The recursive resolver does the walking.
Usually operated by your ISP or a public DNS provider, it follows referrals and caches the final answer for its time-to-live.
03
AFTER DNS
The name is only the start.
Prove and encrypt.
The server presents a certificate. The parties agree on keys so intermediaries cannot read or silently alter the exchange.
Ask for a resource.
The browser sends a method, path, headers, and preferences. The server returns status, headers, and bytes.
Turn bytes into pixels.
HTML becomes structure, CSS becomes style, JavaScript adds behavior, and more requests often follow.
THE WHOLE IDEA
A URL is a question.
The web is the chain of systems that answer it.
NAME→ADDRESS→CONNECTION→REQUEST→PIXELS
NEXT EXPLANATIONWhy a positive test can be wrong →