Great question! When you type a URL like "google.com," the request doesn't go straight to the server. First, your browser checks its cache, then the OS cache, and if nothing's there, it hits a DNS server to get the IP.
After DNS resolves the domain, your browser sends the request to that IP. But wait—there's more! If the site uses HTTPS (which most do), there's a TLS handshake first to encrypt the connection.
Load balancers and CDNs add another layer—they distribute requests to different servers based on location or traffic. So, where does the request of a url get sent? It’s a whole journey!
Tools like Wireshark or Chrome DevTools can help you see this in action.
After DNS resolves the domain, your browser sends the request to that IP. But wait—there's more! If the site uses HTTPS (which most do), there's a TLS handshake first to encrypt the connection.
Load balancers and CDNs add another layer—they distribute requests to different servers based on location or traffic. So, where does the request of a url get sent? It’s a whole journey!
Tools like Wireshark or Chrome DevTools can help you see this in action.