TECHNOLOGY · 4 MIN READ

A clearer picture of how the web connects.

Opening a page feels immediate. Underneath, a few distinct pieces work together to make the connection.

A name is easier to remember

A domain name gives a website a readable address. DNS helps a device find the network addresses associated with that name. A browser or operating system may keep recent answers in a cache, so it does not have to repeat the lookup every time.

This is why a name and an address are related but different. A website can move between servers while keeping its name, and a single server can host several websites.

An encrypted connection adds trust

With HTTPS, a browser checks the server's certificate against the requested hostname and the browser's trusted certificate authorities. The connection then protects the requests and responses while they travel between those endpoints.

A valid certificate confirms an important part of that connection. It does not, by itself, establish that every claim on a website is accurate or that every link is a good idea to follow.

The page is a collection of requests

After retrieving the main document, a browser may request stylesheets, images, fonts, and other resources. A small page with few dependencies has fewer pieces that can be delayed or unavailable. That is one reason a simple website can remain pleasant to use on a slow connection.

When something fails, asking which piece failed is more helpful than treating the whole journey as a single step: finding the address, establishing the connection, checking the certificate, or fetching the content.

Back to the notebook