Download websites that use Amazon SES

About Amazon SES

Email infrastructure is picked once, wired into an application, and then left alone for years, which makes it a slow moving signal compared with anything a marketing team can install in an afternoon. Amazon SES belongs to that class of decision. Amazon SES is an Email service from Amazon, released in 2011 on a Proprietary basis, and it delivers mail on behalf of an application instead of rendering anything a visitor would notice. A site that sends through SES looks, in a browser, like a site that sends through nothing at all. Detection therefore rests on the records a domain publishes to authorise its sender rather than on page markup, and that distinction shapes how the count below should be read.

As of October 2026 we associate Amazon SES with 660,667 domains. United States accounts for 392,325 of those, and .com is the suffix running through the group. The geographic weight is unsurprising for a service sold inside a cloud platform whose commercial centre sits in the same market.

What SES presence actually tells you is that somebody with access to the codebase made the sending decision. Marketing suites are bought by marketing teams and installed through a tag manager. SES is added by a developer, usually alongside other services from the same provider, and usually because the traffic is transactional rather than promotional. A domain authorised for SES is a domain where password resets, receipts, and system notifications flow through infrastructure billed by volume. Reading that as a proxy for engineering maturity is fair. Reading it as a proxy for marketing spend is not.

The list is useful to a fairly specific set of readers. Competing sending platforms use it to size the population they could win and to find domains whose sending is already programmatic rather than manual. Deliverability consultants use it to build a book of business. Supply chain and security researchers use it to map how many organisations carry a hard dependency on a single provider for a function they cannot operate without. A per-domain lookup answers whether one company sends this way. A downloadable list answers which companies do, sliced by country, by suffix, and by the rest of the stack on the same domains, and compared against an earlier snapshot it shows movement into and out of the platform.

The honest caveat is that this is a floor rather than a census. Sending infrastructure is only visible where a domain publishes it, so an organisation that routes mail through a platform which itself runs on SES is either counted under that platform or not counted at all. Records drift in the other direction too, because an authorisation can sit in place long after the traffic behind it stopped. And nothing in this field reports volume. A dormant side project and a company sending at scale appear here as the same single row.