Amazon uses Marketo for marketing email and Amazon SES for transactional/notifications. They rank #24 in the Tranco list of most-popular domains. We've also observed sends via 3 other providers: Salesforce MC, Pardot, Acoustic. Email goes out from 9 different subdomains. Their email authentication setup is solid (score 95/100). We've recorded 2 ESP changes since first observing this brand.
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 10 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to 
p=quarantine means receivers actively block or quarantine spoofed mail.
SPF alignment: 92% of observed emails use an aligned return-path (bounces.amazon.com, bounce.email.health.amazon.com, corpmail.amazon.com); the rest use third-party paths (amazonses.com, gmail.com, us-west-2.amazonses.com) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 590 observed emails sign with a domain aligned with amazon.com (amazon.com, email.health.amazon.com, about.amazon.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 99% TLS 1.3 (across 356 sends).
Delivery: fast — 99% of emails in the last 7 days arrive in under 10 seconds (across 115 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Salesforce MC 10 Pardot 5 Acoustic 1ESPs 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.
ESPs this brand has authorized in their SPF record. We confirm them with a green ✓ only after seeing recurring use (3+ emails across 2+ days). Until then they stay here — either we haven't observed any email yet, or we've seen a handful but not enough to call them a regular sender for the brand.
Probed: amazon.com, bounces.amazon.com, bounces.gift-cards.amazon.com, amazonses.com, gmail.com, us-west-2.amazonses.com, bounce.email.health.amazon.com, mail.brandprotection.amazon.com, corpmail.amazon.com, notifications.pharmacy.amazon.com, red-robot.net, bounce.s12.exacttarget.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 | 450 | 93.0% |
| promotions | 33 | 6.8% |
| spam | 1 | 0.2% |
Placement observed in Outlook / Microsoft 365 mailboxes. Focused Inbox splits mail into two tabs, "Focused" (inbox) and "Other", plus Junk. 100% reached the Focused inbox across 1 observed email.
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 % |
|---|---|---|---|---|---|
| Pardot | 4 | 75.0% | 0.0% | 25.0% | |
| Marketo | 32 | 84.4% | 15.6% | 0.0% | |
| Amazon SES | 413 | 93.2% | 6.8% | 0.0% | |
| Acoustic | 1 | 100.0% | 0.0% | 0.0% | |
| Salesforce MC | 9 | 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 amazon.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 54.240.13.63 | a13-63.smtp-out.amazonses.com |
10 | — | Check → |
| 54.240.13.49 | a13-49.smtp-out.amazonses.com |
9 | 4 | Check → |
| 54.240.13.155 | a13-155.smtp-out.amazonses.com |
8 | 2 | Check → |
| 54.240.13.93 | a13-93.smtp-out.amazonses.com |
7 | — | Check → |
| 54.240.13.48 | a13-48.smtp-out.amazonses.com |
7 | — | Check → |
| 54.240.13.163 | a13-163.smtp-out.amazonses.com |
7 | — | Check → |
| 54.240.13.29 | a13-29.smtp-out.amazonses.com |
7 | 1 | Check → |
| 54.240.13.21 | a13-21.smtp-out.amazonses.com |
7 | — | Check → |
| 54.240.13.67 | a13-67.smtp-out.amazonses.com |
7 | 1 | Check → |
| 54.240.13.161 | a13-161.smtp-out.amazonses.com |
7 | — | Check → |
| 54.240.13.25 | a13-25.smtp-out.amazonses.com |
7 | 1 | Check → |
| 54.240.13.51 | a13-51.smtp-out.amazonses.com |
7 | 2 | Check → |
| 54.240.13.175 | a13-175.smtp-out.amazonses.com |
7 | — | Check → |
| 54.240.13.156 | a13-156.smtp-out.amazonses.com |
6 | — | Check → |
| 54.240.13.103 | a13-103.smtp-out.amazonses.com |
6 | — | Check → |
| 54.240.13.5 | a13-5.smtp-out.amazonses.com |
6 | — | Check → |
| 54.240.13.39 | a13-39.smtp-out.amazonses.com |
6 | 3 | Check → |
| 54.240.13.125 | a13-125.smtp-out.amazonses.com |
6 | — | Check → |
| 54.240.11.126 | a11-126.smtp-out.amazonses.com |
6 | — | Check → |
| 54.240.13.118 | a13-118.smtp-out.amazonses.com |
5 | — | Check → |
| 54.240.13.154 | a13-154.smtp-out.amazonses.com |
5 | 2 | Check → |
| 54.240.13.141 | a13-141.smtp-out.amazonses.com |
5 | — | Check → |
| 54.240.13.4 | a13-4.smtp-out.amazonses.com |
5 | 1 | Check → |
| 54.240.13.62 | a13-62.smtp-out.amazonses.com |
5 | — | Check → |
| 54.240.13.20 | a13-20.smtp-out.amazonses.com |
5 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
amazon.com | Amazon SES 612 Marketo 29 Acoustic 1 | |
email.health.amazon.com | Salesforce MC 10 | |
about.amazon.com | Marketo 6 | |
brandprotection.amazon.com | Pardot 4 | |
business.amazon.com | Amazon SES 4 | |
ads.amazon.com | Amazon SES 4 | |
gift-cards.amazon.com | Amazon SES 1 | |
ampay.amazon.com | Pardot 1 | |
pharmacy.amazon.com | Amazon SES 1 |