When you type a website's address into your browser and hit Enter, a lot happens behind the scenes in a fraction of a second — a chain of steps most ordinary users never see, but that anyone who wants to build or manage a website needs to understand.
Step 1: Domain registration
It all starts with a name (like example.com) purchased from a domain registrar. This name is purely a human-readable label — computers work with IP addresses, not names.
Step 2: DNS, the internet's phone book
The DNS (Domain Name System) does exactly this job: translating a readable name (example.com) into the actual IP address of the server the site is hosted on. When you type the address, your browser sends this query to a DNS server and gets back the IP address — usually in a few milliseconds.
Step 3: Hosting, the real home of the site's files
That IP address belongs to a server — an always-on computer connected to the internet, storing the site's files (HTML, images, code). This server can belong to a hosting company, a cloud service like AWS, or even a personal server.
Step 4: The HTTP request
Your browser now sends an HTTP request (or its encrypted version, HTTPS) to that server, saying "send me the site's homepage." The server, usually through web server software like Nginx or Apache, receives the request, processes it, and returns a response.
Step 5: Backend vs. Frontend
If the site is simple and static, the server returns the ready-made HTML file directly. If the site is dynamic — like an online store — a server-side program (the backend, e.g., PHP or Node.js) first talks to a database, fetches the needed data (like a product list), and then builds the final HTML. This part is called the backend. What you see and interact with in the browser — the look, buttons, animations — is the frontend, built with HTML, CSS, and JavaScript.
Step 6: Rendering in the browser
Your browser reads the received HTML, builds the page structure, applies CSS for appearance, and runs JavaScript for interactivity (like clicking a button) — the result is the page you see, usually less than a second after hitting Enter.
Why does HTTPS matter?
The small lock icon next to a site's address shows the connection between your browser and the server is encrypted (HTTPS) — meaning even if someone sees the network traffic (exactly what this site's Wireshark tutorial covers), they can't read the actual content exchanged.
Summary
Understanding this chain — domain, DNS, hosting, HTTP, backend/frontend — is the foundation everything else builds on, whether your next step is web design or backend development.
Blog