Networking basics

How the Internet Works: From a Click to Your Screen

Follow a website request through Wi-Fi, DNS, routers and servers, and see how the pieces work together.

The Internet connects many independently run networks

Your home network connects to an Internet service provider. Providers connect to other networks, including those serving offices, universities and data centres. Common protocols let these different systems exchange information.

No single company owns the whole Internet. Its physical connections include fibre, copper and radio links. The Web is one service that uses this network; email, online games and many other applications use it too.

Internet Society: how the Internet works

1. Your device reaches the local network

When you open a website, your phone or computer uses a local connection such as Wi-Fi or Ethernet. A gateway provides a path toward other networks through your Internet provider. A mobile connection uses the operator’s radio and core network instead.

Wi-Fi and Internet access are separate things. Your device can be connected to a working access point while the upstream connection is down. That is why a full Wi-Fi indicator does not prove that a website can be reached.

2. DNS helps find the website’s address

You type a readable name such as gloman.gr. DNS helps resolve that name to an IP address that the connection can use. Your device or its DNS resolver may already have a cached answer; otherwise, the resolver asks the appropriate DNS servers.

DNS supplies addressing information. It does not carry the website’s pictures or page content. A DNS failure can prevent a name from working even when the destination server is running.

Cloudflare: how DNS works

3. Data travels in packets

Network communication divides data into small units called packets. Routers forward IP packets toward their destinations, one hop at a time. Their routing tables guide the next step; a router does not need a complete street-by-street map for every packet.

Packets can be lost or arrive out of order. Transport protocols such as TCP, or QUIC used by HTTP/3, provide mechanisms for reliable delivery. Paths can change, but packets do not have to take different routes, and the return path need not match the outward path.

Between independently operated networks, BGP exchanges reachability information. Peering allows networks to exchange traffic directly, while transit provides access through another network. These arrangements affect the paths available to your connection.

4. HTTPS protects the conversation

For an HTTPS website, TLS protects the connection’s contents against reading or modification in transit and helps the browser authenticate the server using certificates. The browser then exchanges HTTP requests and responses over the protected connection.

Encryption protects the connection; it does not prove that a site’s claims are true or its business is trustworthy. The server handling your request can still read the data you send to it.

Cloudflare: Transport Layer Security

5. A server or CDN returns the content

The request may reach the site’s origin server or a CDN that can serve a cached copy. An application might query a database before replying. Your browser assembles the returned HTML, styles, scripts and images into the page you see, often requesting more files along the way.

A CDN can reduce repeated work and shorten delivery paths for suitable content. Personalised responses may still require the application. A page can therefore feel slow because of Wi-Fi, routing, the server, a database or browser work, even if the access line has plenty of bandwidth.

Bandwidth and latency answer different questions

Bandwidth describes how much data a connection can carry per unit of time. Latency describes delay. A large video download benefits from capacity; an application exchanging many small requests can be very sensitive to delay.

To investigate a slow service, test the local connection, name resolution, path and application separately. Changing one component only helps if it addresses the actual bottleneck.