What Actually Happens in the 2 Seconds After You Hit Enter

You type "google.com" and press Enter. A page appears. Feels instant. But in that blink — roughly 2 seconds — your browser just orchestrated a relay race across dozens of machines spanning multiple continents. I find it genuinely wild that most web developers ship code every day without knowing what happens between keystroke and pixel. So here's the full chain, no hand-waving. Step 1: DNS — Translating Names to Numbers Your browser doesn't know what "google.com" means. Computers speak IP addresses, not words. So the first job is translation. The browser checks its own cache first. Then the OS cache. Then your router's cache. If nobody has the answer, the query goes to a recursive DNS resolver — usually run by your ISP or a service like Cloudflare (1.1.1.1) or Google (8.8.8.8). That resolver walks the DNS hierarchy: root server → .com TLD server → Google's authoritative nameserver. Each step narrows down until someone says "google.com lives at 142.250.70.14." The whole lookup typically