21/01/2026
Behind the Scenes: What Happens When You Enter Google[dot]com
Most of us hit Enter and expect the page to load instantly, but under the hood, a surprisingly intricate chain of events fires off in milliseconds.
Here’s a quick tour of what actually happens:
1. The journey starts the moment you type “google. com” into the address bar.
2. The browser checks everywhere for a cached IP: Before touching the network, your browser looks through multiple cache layers, browser cache, OS cache, router cache, and even your ISP’s DNS cache.
A cache hit means an instant IP address. A miss kicks off the real journey.
3. Recursive DNS resolution begins: Your DNS resolver digs through the global DNS hierarchy:
- Root servers
- TLD servers (.com)
- Authoritative servers for google. com
4. A TCP connection is established: Your machine and Google’s server complete the classic TCP 3-way handshake:
- SYN → SYN/ACK → ACK
Only after the connection is stable does the browser move on. TLS handshake wraps everything in encryption. By the end of this handshake, a secure HTTPS tunnel is ready.
5. The actual HTTP request finally goes out: Google processes the request and streams back HTML, CSS, JavaScript, and all the assets needed to build the page.
6. The rendering pipeline kicks in:
Your browser parses HTML into a DOM tree, CSS into a CSSOM tree, merges them into the Render Tree, and then:
- Lays out elements
- Loads and executes JavaScript
- Repaints the screen
8. The page is fully loaded.
Over to you: What part of this journey was most surprising the first time you learned how browsers work?
Cre: Alex Xu
![Behind the Scenes: What Happens When You Enter Google[dot]comMost of us hit Enter and expect the page to load instantly,...](https://img5.computers1000.com/874/741/904497658747417.jpg)
