This one goes deep. Understanding what happens in those few milliseconds between hitting Enter and seeing a webpage is one of those things that makes you look at the internet completely differently. Let's walk through it properly.
The Journey of a Single Request
Step 1 — You type google.com and hit Enter
Simple enough. But what happens next is anything but.
Step 2 — DNS Lookup: Finding the Address
Your browser doesn't understand names — it understands IP addresses. So first it needs to translate google.com into something like 142.250.195.46. It checks in this order:
Local cache → ISP → Root server → gets the Mumbai IP (or wherever you're closest to)
Think of DNS as the internet's phonebook. You give it a name, it gives you a number.
Step 3 — TCP Handshake: Building the Road
Before any data moves, a reliable connection needs to be established. This is the TCP handshake — using SYN and ACK messages back and forth to essentially say "hey, can you hear me?" — "yes, can you hear me?" — "yes, let's go." Think of it as road construction before traffic can flow.
Step 4 — TLS Handshake: Locking the Road
The road exists, but it's not secure yet. The TLS handshake encrypts the connection so nobody in the middle can read what's being sent. Once this is done, HTTP becomes HTTPS — the S literally stands for the TLS layer wrapping the connection.
Step 5 — HTTP Request: The Actual Conversation
Now the browser finally asks for the page. "Give me google.com." The server responds with HTML, CSS, JavaScript — everything needed to render what you see.
Step 6 — Page Rendered
Your browser takes all that data and paints the page. What feels instant is actually all six of these steps happening in milliseconds.
The 2026 Cool Fact — 0-RTT
If you've visited Google recently, Steps 3 and 4 can happen almost simultaneously — this is called 0-RTT (Zero Round-Trip Time). It's a feature in TLS 1.3 that lets your browser skip the full handshake on reconnection and send data immediately. The result? The site feels like it loaded instantly. This is why returning visits always feel faster than first visits.
The Glossary — Security & Protocol Terms
TLS — Transport Layer Security. The current standard for encrypting connections.
SSL — Secure Sockets Layer. The older, now-deprecated version of TLS. You'll still hear people say "SSL certificate" but they almost always mean TLS at this point.
HTTP — Hypertext Transfer Protocol. The language browsers and servers use to talk.
HTTPS — HTTP + TLS. The secure version. Always look for this in your browser bar.
HSTS — HTTP Strict Transport Security. Forces your browser to only use HTTPS for a site — even if you type http:// manually. A site can tell your browser "never connect to me without encryption."
0-RTT — Zero Round-Trip Time. High-speed reconnection feature in TLS 1.3.
The Glossary — Networking & Infrastructure
IP — Internet Protocol. The addressing system of the internet.
IPv4 / IPv6 — Version 4 uses addresses like 192.168.1.1. Version 6 was introduced because we ran out of IPv4 addresses — there are only about 4 billion of them and the internet has way more devices than that now.
TCP — Transmission Control Protocol. Reliable, ordered delivery. The "road builder."
UDP — User Datagram Protocol. Faster but doesn't guarantee delivery — used in HTTP/3, video calls, gaming. Speed matters more than perfection there.
DNS — Domain Name System. Translates google.com into an IP address.
ISP — Internet Service Provider. The company you pay for internet access.
The Glossary —** Advanced Concepts**
MUX (Multiplexing) — Sending multiple signals through one path simultaneously. HTTP/2 and HTTP/3 use this so multiple files load in parallel over a single connection instead of queuing up.
GGC — Google Global Cache. Google literally places their own servers inside ISP buildings around the world so your YouTube video doesn't have to travel halfway across the planet. Fewer hops, faster delivery.
IoT — Internet of Things. Smart devices — cameras, thermostats, fridges — anything connected to the internet that isn't a traditional computer.
TLD — Top-Level Domain. The .com, .org, .in part of a URL.
SYN / ACK — Synchronize / Acknowledgement. The specific messages exchanged during the TCP handshake.
RTT — Round-Trip Time. How long it takes a signal to travel to a server and come back. Lower is better.
Domain Hierarchy — Reading Right to Left
Most people read a domain left to right — but the internet reads it right to left. Here's the full tree:
Root Level — The invisible dot at the very end of every URL (google.com.). All DNS lookups start here.
TLD (Top-Level Domain) — The extension after the last dot. .com, .org, .in. Categorises the site by purpose or region.
SLD (Second-Level Domain) — What most people call "the website name." The google in google.com.
Subdomain (Third Level) — Prefixes that organise sections of a site. The docs in docs.google.com.
Lower Levels — Technically up to 127 levels deep, though more than four is rare in practice. Something like dev.blog.google.com would be a fourth-level domain.
Special Case — ccSLD — Some countries add a category at the second level. So instead of google.com, you get google.co.uk — where .uk is the country, .co is the category, and google is pushed to the third level.
SMTP, POP3, and IMAP — Email Has Three Jobs
Here's something most people don't realise — email uses different protocols for sending vs receiving, and they're completely separate:
SMTP (Simple Mail Transfer Protocol) — only for sending mail. That's its one job. When you hit send, SMTP takes over.
POP3 (Post Office Protocol 3) — for reading mail. Downloads emails to your device and typically removes them from the server. Old school.
IMAP (Internet Message Access Protocol) — also for reading, but smarter. Keeps emails on the server and syncs across all your devices. This is why your phone and laptop show the same inbox.
DHCP — How Your Device Gets an IP Address Automatically
Every device on a network needs an IP address. But you've never manually typed one in (probably). That's DHCP doing its job silently.
When you connect your phone to your router, your phone is the host — and it needs an IP, a subnet mask, a default gateway, and DNS settings to function on the network. DHCP handles all of that automatically through a four-step process called DORA:
Discover — your device shouts "is there a DHCP server here?"
Offer — the router replies "yes, here's an IP you can use"
Request — your device says "great, I'll take that one"
Acknowledge — the router confirms "it's yours"
One network, one default gateway, one IP address assigned cleanly — and just like that your device is on the internet without you having to configure anything.
Top comments (0)