On 29 May, AWS announced that Amazon SES now offers “inbox placement metrics and blocklist monitoring.” The understated tone made it sound like a dashboard update was launched. Read the documentation behind the announcement closely, as we have, and it’s something considerably larger: it appears that Amazon has quietly assembled a full deliverability monitoring suite, a seed-testing network, and an email validation service, and bolted all three into the SES console as a paid subscription called global deliverability.
One sentence in the developer guide caught our attention. Global deliverability provides analytics “across every provider your domains send through, not just Amazon SES.” However we are balancing this with the fact that Amazon did previously enter and ultimately withdrew from its attempts to commercialise deliverability dashboards (AWS Pinpoint c. 2019). Lessons have likely been learned from that though, and we understand from industry sources that Amazon partnered with established players to build this.
It is really important to note that this is not SES reporting on SES however. Amazon is offering to monitor your domain’s deliverability wherever your mail goes out, including through competing platforms. That is not a feature of an ESP. That is the product Validity, GlockApps, Inbox Monster and a dozen others sell as their entire business, now living inside the AWS console next to the rest of your infrastructure bill.
What’s actually in the box
Four components, per the documentation.
Campaign analytics detects campaigns from your monitored domains and reports inbox rate, spam rate, open rate and delete rate, broken down by mailbox provider, “even when they leave through a non-Amazon SES provider.” Detected is the operative word: the system identifies campaigns, their projected volume, and first and last seen dates from sampled data, which is the behaviour of a data panel, not a mail log.
Inbox placement rates give hourly-updated, ISP-level placement for monitored domains, with the documentation’s repeated caveat that figures are “based on a representative sample of data and do not reflect the full volume of emails sent.”
Inbox placement tests are genuine seed tests: SES sends your candidate campaign to seed accounts at major mailbox providers and returns inbox, spam and missing percentages per ISP within two to four hours. Subscriptions include a monthly test quota with overage charges beyond it.
Blocklist monitoring checks dedicated IPs and sending domains against “the industry’s major blocklist operators” hourly, with listing reasons, delisting procedures, and alerts through the VDM Advisor and EventBridge.
And tucked into the same documentation set is a fifth piece the announcement didn’t mention at all: Email Validation, an SES feature that checks addresses for syntax, DNS validity, mailbox existence, role accounts, disposable domains and random-string patterns, returning high, medium or low confidence verdicts.
It includes an Auto Validation mode that “automatically reviews all outbound email addresses and only delivers messages to recipients that meet your selected delivery likelihood threshold.” That is real-time list hygiene with automatic suppression, the core product of the verification industry, running at the point of send.
The questions Amazon hasn’t answered
Where does the placement data come from? Spam-folder rates, open rates and delete rates at Gmail and Microsoft are not observable from the sending side. They come from panels: consumer inbox tools, mailbox-connected apps, purchased signal. The documentation attributes everything to “analytics” and never names a source, a panel size, or coverage by provider. For a product whose entire value is the accuracy of a percentage, that’s a meaningful omission.
Whose seed network, and which blocklists? “Major blocklist operators” is doing a lot of unspecified work. Spamhaus & SURBL listings matter enormously; many of the public blocklists matter not at all. Senders evaluating this against established tools deserve the list. AWS remains completely opaque about its data panels. Their documentation attributes the spam folder placement metrics purely to “samples of industry data.” They do not disclose the panel size, regional coverage, or the identity of the partners involved.
One thought that did keep coming back to me when reviewing features and functionality, Amazon now offers to observe how your campaigns perform when sent through its competitors. Useful for senders, for sure, but it is a lot of data to be potentially sharing. Invariably it means the world’s largest cloud provider gets to build a panel-eye view of email traffic across rival platforms. The competitive-intelligence implications of that probably deserves significant attention.
Who is going to feel this?
The squeeze we described in our Postmaster Tools coverage just gained a second jaw. In the same fortnight, Gmail began issuing plain-language deliverability verdicts from above, and the largest sending platform on the internet absorbed placement testing, blocklist monitoring and list validation from below. The standalone deliverability and hygiene vendor is being compressed toward what platforms can’t replicate: cross-provider neutrality, methodology you can interrogate, human expertise, and consulting.
We won’t pretend this is abstract. Verification specialists, including firms in our own membership, now compete with a checkbox in the SES console, in the same way monitoring vendors now compete with a bundled subscription. The honest counterargument is also the real one: a checkbox doesn’t tell you why, doesn’t see your non-AWS reputation problems in context, doesn’t get Spamhaus delistings, and Amazon’s own caveats concede its numbers are samples, not censuses. The vendors that thrive from here will be the ones that can demonstrate, publicly and specifically, what their data sees that Amazon’s panel doesn’t.
Also worth remembering when SES first launched there was a lot of doom and gloom about it being the end of ESPs and transactional email platforms. It was not, and this will not in itself be the end of traditional deliverability suites and services, not by a long shot.
There’s also a sharp edge for SES customers. The launch landed three weeks after Kaspersky documented criminals hijacking SES accounts at scale through leaked AWS keys, mail that inherits the victim’s reputation and passes every authentication check. Blocklist alerts and placement drops are precisely how a customer would discover their keys had leaked. Amazon now sells you the smoke detector for a fire we reported burning on its own infrastructure. Worth having; better still alongside not leaving the keys in the repo.
If you are looking to enable the suite then optimised shared delivery, which is on by default, can preemptively delay your mail to protect reputation. Amazon’s own documentation says not to enable it for time-critical workloads. Read the defaults before you accept them.
We will try and follow up with AWS about panel sourcing, seed coverage and the monitored blocklists, and we’ll report what comes back. We will also look to enable this on our own account and report back in due course about our own findings. In the meantime, the conclusion stands on the documentation alone: the era of deliverability monitoring as a separate purchase from your sending platform may well be coming to a close for some, and it seems to be coming from both ends this quarter.
Sources: AWS What’s New, 29 May 2026; Amazon SES Developer Guide, Virtual Deliverability Manager and global deliverability sections.
Disclosure: emailexpert’s membership includes companies in the deliverability monitoring and email verification markets discussed here, including ZeroBounce and Bouncer. Coverage is editorially independent.
