Aws uses Amazon SES as their primary email service provider. They rank #3,983 in the Tranco list of most-popular domains. Their email authentication setup is solid (score 95/100). Missing: one-click unsubscribe.
Amazon SESAuthentication signals observed in this brand's emails. SPF, DKIM and DMARC are the standard sender-authentication stack — see the DMARC policy below for whether spoofing is actually blocked or just monitored. One-click unsubscribe meets Google & Yahoo's bulk-sender requirements.
SPF / DKIM / DMARC above reflect the last 1 email we've observed. DMARC policy is read live from DNS.
DMARC reports sent to aws.com. Policy
p=quarantine means receivers actively block or quarantine spoofed mail.
SPF alignment: 48% of observed emails use an aligned return-path (user-notifications.email.aws.com); the rest use third-party paths (amazonses.com) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 29 observed emails sign with a domain aligned with aws.com (aws.com). DKIM authenticates the visible From — supports DMARC directly.
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
None — only the primary ESP(s) shown aboveESPs we've seen sending email for this brand. Green = confirmed by SPF, sender IP rDNS, or known infra pairing (label shows the source). Grey = observed but not yet confirmed by SPF or PTR.
No additional ESPs authorized in the brand's SPF beyond the confirmed senders above.
Probed: aws.com, user-notifications.email.aws.com, amazonses.com
Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.
| Folder | Count | Share |
|---|---|---|
| inbox | 38 | 100.0% |
Which ESP's emails are landing where. Sorted by spam % so problem senders surface first. Brands using one ESP for marketing and another for transactional often see very different placement profiles per ESP. Per-ESP folder data only started being captured recently — counts here may be smaller than the total above until backfill catches up.
| ESP | Emails | Placement | Inbox % | Tabs % | Spam % |
|---|---|---|---|---|---|
| Amazon SES | 32 | 100.0% | 0.0% | 0.0% |
Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.
IP addresses aws.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 54.240.9.109 | a9-109.smtp-out.amazonses.com |
8 | 1 | Check → |
| 54.240.14.59 | a14-59.smtp-out.amazonses.com |
5 | — | Check → |
| 54.240.9.12 | a9-12.smtp-out.amazonses.com |
4 | — | Check → |
| 54.240.9.63 | a9-63.smtp-out.amazonses.com |
3 | — | Check → |
| 54.240.9.14 | a9-14.smtp-out.amazonses.com |
3 | — | Check → |
| 54.240.9.29 | a9-29.smtp-out.amazonses.com |
2 | — | Check → |
| 54.240.14.41 | a14-41.smtp-out.amazonses.com |
2 | — | Check → |
| 54.240.9.27 | a9-27.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.14.40 | a14-40.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.9.38 | a9-38.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.9.98 | a9-98.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.9.91 | a9-91.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.9.11 | a9-11.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.14.55 | a14-55.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.14.57 | a14-57.smtp-out.amazonses.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
aws.com | Amazon SES 38 |
