Ever wondered what happens behind the scenes when you type a web address and hit enter? At first glance, it feels instant, but a lot of steps happen in just a few milliseconds.
Websites and Servers
A website is nothing but a collection of files. HTML, CSS, JavaScript, and media, that instruct your browser on how to display the site.
These files live on a server. A server is a powerful computer connected to the internet 24/7. Hosting simply means storing these files on the server so anyone around the world can access them.
URLs and Protocols
https://abc.com
HTTPS → This is the protocol, the set of rules your browser and server use to communicate. Think of it as the language they speak. HTTPS is just a secure (encrypted) version of HTTP.
abc.com → This is the domain name.
Domains and IP Addresses
A domain name like abc.com is actually a human-friendly way to point to an IP address.
An IP address is a unique identifier that tells the browser exactly which server to connect to.
Every device on the internet (including your phone and laptop) has its own IP address.
Since humans find names easier to remember than numbers, we use domains instead of typing IPs directly.
DNS – The Internet’s Phonebook
This is where DNS (Domain Name System) comes in. DNS is like a phonebook that stores domain names and their corresponding IP addresses.
Here’s how your browser finds the IP for a domain:
Browser cache → First, it checks if it has the domain saved locally.
OS cache → If not found, it asks the operating system (Windows, Android, etc.).
DNS resolver (usually your ISP) → Still not found? The OS forwards the query to the DNS resolver.
Recursive lookup → If the resolver doesn’t have the answer cached, it starts asking other DNS servers until it finds the correct IP.
Establishing the Connection
Once the IP is found, your browser connects to the server. But before sending data, both sides need to “shake hands”.
This is called the TCP 3-way handshake, which ensures both devices are ready to talk to each other.
Requesting and Rendering the Page
After the handshake, the browser sends an HTTP GET request to ask the server for the webpage.
The server responds with the files.
The browser’s rendering engine interprets the code and displays the page on your screen.
Final Thoughts
The next time you click on a link, remember: behind that instant load is a fascinating chain of steps, from DNS lookups to handshakes, all working together to bring the internet to life.
Top comments (0)