System Design

Behind the Scenes: What Happens When You Enter Google.com 🌐

Posted by Aryan Jaswal on 19 April 2026

Ever wonder what happens in the milliseconds between typing google.com and the search page loading?

Behind the Scenes: What Happens When You Enter Google.com 🌐 featured image

We do it dozens of times a day. You open your browser, type google.com, hit Enter, and in less than a second, the search engine appears.

But have you ever paused to think about the massive digital marathon that happens in those mere milliseconds?

The journey from a simple URL to a fully rendered webpage is a masterpiece of modern computer science. Let’s take a quick tour behind the scenes and break down the complex pipeline of the web. 👇

1. The Cache Hunt: Before Touching the Network 🔍

The journey starts the exact moment you type “google.com” into your address bar. But before your browser even reaches out to the open web, it looks for a shortcut. It checks multiple cache layers for a saved IP address:

  • Browser Cache: Has the browser saved it recently?
  • OS Cache: Does your operating system know it?
  • Router Cache: Is it saved on your local network?
  • ISP Cache: Does your Internet Service Provider have it on file?

A cache hit means an instant IP address. A cache miss kicks off the real journey.

2. DNS Resolution: The Internet’s Phonebook 📖

If the IP isn't cached, your DNS resolver starts a recursive search through the global DNS hierarchy to translate the human-readable "google.com" into a machine-readable IP address. It digs through:

  • Root Servers: The top of the internet's directory.
  • TLD Servers: The servers managing .com domains.
  • Authoritative Name Servers: The specific servers that hold the exact IP address for Google.

3. The TCP 3-Way Handshake: Making Contact 🤝

Once the IP address is resolved, your machine and Google’s server need to establish a reliable connection. They complete the classic TCP 3-way handshake:

  • SYN: Your computer asks to connect.
  • SYN + ACK: Google's server acknowledges and agrees.
  • ACK: Your computer confirms the connection.

4. The TLS Handshake: Securing the Tunnel 🔒

Only after the TCP connection is stable does the browser move on to security. The TLS Handshake wraps your connection in encryption, ensuring that no one can eavesdrop on your search queries. By the end of this handshake, a secure, encrypted HTTPS tunnel is ready.

5. The HTTP Request & Server Response 📨

With the secure tunnel built, the actual HTTP GET request finally goes out. Google’s servers process your request at lightning speed and stream back the raw materials needed to build the page: HTML, CSS, and JavaScript.

6. The Rendering Pipeline: Painting the Screen 🎨

Now, your browser goes to work assembling the pieces. It doesn't just slap code on the screen; it follows a strict rendering pipeline:

  • Parsing: It parses the HTML into a DOM Tree (the structure) and the CSS into a CSSOM Tree (the styling).
  • Merging: These are merged to create the Render Tree.
  • Executing: The browser’s engine loads and executes the JavaScript.
  • Painting: Finally, it calculates the layout and visually repaints the pixels onto your screen.

7. Page Successfully Loaded ✅

And there it is. The search bar is blinking, waiting for your query. All of this data routed across the globe, validated, secured, downloaded, and painted—usually in under 500 milliseconds.