The Internet vs. The Web

Two terms people often use interchangeably are actually different things. The internet is the global physical infrastructure: the cables, routers, servers, and wireless links that connect billions of devices. The World Wide Web is one service that runs on top of the internet — a system of linked documents and resources accessed via browsers. Email, video calls, and online gaming are also internet services, but separate from the Web.

Step 1: You Type a URL

When you type example.com into your browser, the first challenge is that computers don't understand domain names — they communicate using numerical IP addresses (like 93.184.216.34). So your computer must first translate the domain name into an IP address.

This is done by the Domain Name System (DNS) — essentially a globally distributed phone book. Your device queries a DNS resolver (usually provided by your internet service provider or a public service like Google's 8.8.8.8), which looks up the IP address for the domain and returns it to your browser.

Step 2: Establishing a Connection (TCP/IP)

With the IP address known, your browser needs to establish a connection with the server. This uses TCP/IP — the foundational protocol suite of the internet.

  • IP (Internet Protocol) handles addressing and routing — breaking data into packets and sending each one toward its destination, potentially via different paths through the network.
  • TCP (Transmission Control Protocol) ensures reliability — it guarantees that packets arrive, requests resends if they're lost, and reassembles them in the correct order.

A three-way handshake (SYN → SYN-ACK → ACK) establishes the connection between your computer and the server before any data is exchanged.

Step 3: The HTTPS Layer

For secure websites (those using https://), an additional step occurs: a TLS handshake. Your browser and the server agree on encryption methods and exchange cryptographic keys. From this point on, all data between you and the server is encrypted, protecting it from interception. This is why the padlock icon matters — it means your connection is private.

Step 4: Sending an HTTP Request

Now your browser sends an HTTP request to the server. This is a structured text message that says, in effect: "Please send me the resource at this path." The request includes headers with information like your browser type, what file formats you accept, and any cookies associated with the site.

Step 5: The Server Responds

The web server receives the request, processes it (which may involve querying a database, running application code, or simply fetching a static file), and sends back an HTTP response. This includes:

  • A status code (200 = OK, 404 = Not Found, 301 = Redirect, etc.)
  • Response headers
  • The actual content — usually HTML

Step 6: Your Browser Renders the Page

The browser receives the HTML and begins parsing it. As it encounters references to other resources — CSS stylesheets, JavaScript files, images — it sends additional requests to fetch them. Once it has the necessary resources, it builds the Document Object Model (DOM), applies styles, and executes scripts to render the final visual page you see.

All of This in Under a Second

This entire chain — DNS lookup, TCP handshake, TLS negotiation, HTTP request, server processing, data transmission, and browser rendering — typically completes in well under one second for a well-optimized website. It's a remarkable feat of engineering that spans continents, runs on physical infrastructure ranging from fiber optic cables under oceans to wireless signals in your home, and follows a set of open, agreed-upon standards that allow billions of different devices to communicate seamlessly.