HTTP Request Lifecycle Explained — What Really Happens When You Hit Enter

You type https://google.com into your browser and press Enter. In about 200 milliseconds, a fully rendered page appears. But what actually happened in those 200 milliseconds? Most developers — even experienced ones — have a vague idea. ‘DNS happens, then TCP, then… HTTP stuff.’ But if you’re building backends, designing APIs, debugging slow responses, or preparing for system design interviews, ‘vague’ is not good enough. In this post, we’re going to trace every single thing that happens — from the moment you press Enter to the moment the response arrives — explained in plain language with real examples and actual HTTP messages. Let’s go. The 7 Stages at a Glance Before we dive deep into each stage, here’s the full picture: Stage What Happens Who Does It URL Parsing Browser breaks down the URL into parts Browser DNS Lookup Domain name is resolved to an IP address OS + DNS Servers TCP Handshake A reliable connection is established Client + Server TLS Handshake Connection is encrypted (HT