Hosting used to be one line in a tech profile. Now it's an edge network in front, serverless functions behind, and an origin that barely exists. How modern hosting works and how to read it.
Hosting used to be a single answer: the server a site runs on. Now it is a stack of layers: a CDN or edge network in front, serverless functions handling logic, and an origin server that may barely exist. Platforms like Vercel, Netlify and Cloudflare drove the shift, and the layers each leave a fingerprint in a site's headers and request hosts.
Ask what a site is hosted on and the honest answer in 2026 is usually a list, not a name. The page came from an edge node near you, the dynamic bits ran in a function somewhere, and the origin, if there even is one, never saw your request.
From one server to a stack of layers
The old model was simple to read: a site lived on a server, and that server's address told you the host. The new model spreads the work across layers, each optimized for a different job.
| Layer | What it does | Examples | The tell |
|---|---|---|---|
| Edge / CDN | Serves cached pages from near the user | Cloudflare, Fastly | CDN-specific response headers |
| Serverless | Runs logic on demand, no server to manage | Vercel, Netlify, Lambda | Platform headers, function routes |
| Origin | The source, increasingly thin or absent | Traditional servers, object storage | Often hidden behind the edge |
Why it moved this way
Two pressures pushed hosting to the edge. Speed: serving a page from a node near the user beats a round trip to one origin every time. And operations: serverless means no servers to patch, scale, or wake up at 3am. For most teams the trade was easy, which is why the front of the stack is now dominated by a handful of edge platforms. In our index, Cloudflare alone sits in front of a large share of sites.
How to read modern hosting
The clearest tells are in the response headers and the hosts a page talks to. Edge platforms stamp their own headers; serverless platforms expose function routes and platform-specific markers. The origin is often invisible by design, hidden behind the edge, which is itself a signal that a site is running a modern layered stack rather than a single box.
Our directory reports the layers it can see, the CDN and the platform in front, so you can tell an edge-hosted site from a traditional one. It pairs naturally with the framework a site runs, since meta-frameworks and edge hosting tend to travel together.
See the hosting stack behind any site.
Look up a domainFAQ
What is edge hosting?
Serving a site from a network of nodes spread around the world, so each request is answered from a location near the user instead of a single origin server. It cuts latency and absorbs traffic spikes.
What is serverless hosting?
A model where your code runs in on-demand functions managed by a platform, with no server for you to provision or maintain. Platforms like Vercel, Netlify and AWS Lambda handle scaling automatically.
How can I tell what a site is hosted on?
Read the response headers and the hosts the page talks to. Edge and serverless platforms stamp recognizable headers and routes. Because the origin is often hidden behind the edge, a detection tool that reads these layers is the reliable way to see the full hosting stack.
