From DNS to undersea fiber: 10 organizations the web depends on
Get Quartz in your inbox
Free daily briefing on global business news.
From DNS to undersea fiber: 10 organizations the web depends on
A selection of companies that run the internet, plus two nonprofits, behind the domain names, cables, data centers and security certificates few people ever see
Typing a web address and watching a page load feels instant. Inside that brief gap, the request passes through a chain of organizations that most people never see and rarely hear named. Their work goes unnoticed when it functions and becomes visible only when it fails.
The first step is translation. A browser has to turn a name such as qz.com into a numeric IP address that computers use to find each other. That lookup runs through the domain name system, a layered hierarchy of registries and servers coordinated worldwide. Next comes delivery. The page often arrives from a copy stored on a content delivery network server near the reader, not from one distant machine. The site itself may run on computing power rented from a cloud provider rather than hardware its owner bought. The data moves over fiber backbone networks and, between continents, through cables laid on the seabed. An encrypted HTTPS connection depends on a digital certificate issued by a certificate authority.
This list profiles internet infrastructure organizations across 10 entries. It is a selection, not a ranking or a complete roster. Most entries are companies that run the internet's core services as commercial businesses. Two are nonprofits. ICANN coordinates domain names and IP address allocation. Let's Encrypt, a free certificate authority, is run by the Internet Security Research Group.
The reason to know these names is concentration. Many websites rely on the same small group of providers for naming, delivery, hosting and security. When one provider handles a function for many sites, a fault there can reach all of them at once. A configuration error, an outage or a policy decision at a single organization can disrupt services that look unrelated to the people using them.
The slides that follow take each organization in turn. They explain what it does, where it sits on the path between a reader and a website, and what the technical terms around it mean. Some took on their role in the late 1990s, while others arrived more recently.
Cloudflare protects and speeds up websites from its network edge
Cloudflare sits between a website and its visitors, handling traffic before it reaches the site's own servers. In that position, the company combines three services: a content delivery network, a domain name system (DNS) provider and protection against distributed denial-of-service (DDoS) attacks.
Sitting in front of a website has a specific technical meaning. When a site uses Cloudflare as a reverse proxy, visitors connect to Cloudflare's servers rather than directly to the site's origin server. Cloudflare then decides which requests to answer itself and which to pass along. The origin server's real address can stay out of public view.
That position at the network edge is what lets one provider do several jobs at once. Every request to a protected site already flows through its machines. The same servers that deliver content can also inspect incoming requests and filter out unwanted ones.
The content delivery side works through caching. Cloudflare stores copies of files that rarely change, such as images, scripts and style sheets. It serves those stored copies to visitors without asking the origin server for them each time. That cuts the load on the site's own hardware.
DNS is the second layer. Cloudflare can act as the authoritative DNS provider for a domain. That means its servers hold the official records saying which IP address a domain name points to. Lookups for the domain end at Cloudflare's servers, which return the address. A slow or failed DNS answer means a page never starts loading, however healthy the server behind it.
DDoS protection is the third. A DDoS attack floods a target with traffic from many machines at once, often hijacked devices, until it cannot respond to real users. Cloudflare already receives a protected site's traffic. That lets it absorb or drop attack traffic before it reaches the origin.
Combining these roles carries a trade-off. A site that routes its traffic, its DNS and its defenses through Cloudflare depends on Cloudflare staying online. A fault inside the edge network can make the sites behind it unreachable together. Their own origin servers may keep running normally the whole time.
Akamai Technologies built one of the first content delivery networks
Akamai $AKAM Technologies is one of the earliest content delivery networks, a company founded in 1998 out of research at MIT. It runs a distributed network of servers that delivers web content to users from nearby locations.
A content delivery network, or CDN, addresses two problems: distance and demand. Without one, every visitor requests files from the website's own origin server. That server may sit far from many of the people using it.
Distance adds delay. Data crossing continents passes through more networks and more handoffs before it arrives. Each handoff is another point where traffic can slow down or get congested.
Demand creates the second problem. A single origin server has limited capacity. When a large number of people request the same page at once, that server can become overloaded and stop responding.
A CDN spreads the work out. It stores copies of a site's content on servers in many locations. It then directs each user to a nearby server rather than to the origin. The origin handles fewer requests, and the user's data travels a shorter path.
The steering often happens through the domain name system. When a browser looks up a site's name, the CDN can answer with the address of a server close to that user.........
