Download websites that use Amazon Web Services

About Amazon Web Services

The figure on this page will look low to anyone who follows the cloud market, and the gap deserves an explanation before anything else. A crawl sees what a website chooses to reveal on the hostname it was asked about. Put a delivery network or a reverse proxy in front of an origin and the origin vanishes from view. Serve a programming interface, a mobile backend or an internal tool and there is no crawlable homepage to attribute at all. Much of the platform's real estate is invisible by construction, not by oversight.

What survives is a specific and still useful subset. Sites we can attribute usually give themselves away by serving assets from platform endpoints, by resolving into published address ranges, or by leaking a load balancer signature, and those are the same sites an infrastructure adjacent vendor can qualify and reach. Read the row as visible, web facing tenancy. Never read it as market share, and be suspicious of anyone publishing a crawl count as though it were one.

Operated by Amazon since 2006 and sold as Proprietary software, the platform has been around long enough that its footprint contains several distinct generations of architecture at once, from lone instances running a content management system to container estates fronted by managed balancers. A hosting detection flattens all of that into a single row, so the row is a starting point for segmentation rather than a description of what any particular workload actually is.

As of September 2026 we attribute 8,691,057 sites to the platform, 4,815,800 of them in United States, with the set skewing toward .com. Concentration follows corporate registration and the location of the software companies whose products sit on top, not the physical distribution of the regions serving traffic, and the distinction matters a great deal if you are sizing a sales territory from these numbers.

Demand for the list comes from a narrow band of businesses with a clear reason to want it. Observability, cost optimisation, security posture, backup and compliance vendors sell to operators of exactly these workloads. Migration consultancies and competing clouds want accounts to approach. Analysts want concentration risk expressed in domains rather than in reported revenue. Diligence teams want to know what a target company actually runs before the questionnaire comes back describing something tidier.

Any one domain resolves in a second, so the single lookup was never the product. Holding the population lets you filter to your addressable slice, join it to accounts you already have, and compare snapshots to watch movement. A caution belongs on that last point. When a company puts a proxy in front of an existing origin, the attribution disappears from our view, which looks like churn in a time series and is nothing of the kind, so apparent movement should be confirmed before it becomes a claim in a report or a number in a board pack.