Americanexpress uses Salesforce MC for marketing email and SparkPost for transactional/notifications. They rank #2,176 in the Tranco list of most-popular domains. We've also observed sends via Amazon SES. Email goes out from 5 different subdomains. Their email authentication setup is solid (score 100/100). We've recorded 1 ESP change since first observing this brand.
Authentication 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 Return Path / Validity. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: all 35 observed emails use a return-path aligned with americanexpress.com (bounce.member.americanexpress.com, mail.customercommunitycomms.americanexpress.com, bounce.notificationmycredit-guide.americanexpress.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 32 observed emails sign with a domain aligned with americanexpress.com (member.americanexpress.com, customercommunitycomms.americanexpress.com, notificationmycredit-guide.americanexpress.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (across 23 sends).
4 of 12 emails in the last 7 days were delayed beyond 5 minutes (33%) — delays stayed within 5–15 minutes. Slow sends averaged 8 min 3 sec. Healthy senders deliver in under 30 seconds. Consistent delays usually mean greylisting, reputation-based throttling, or receiver-side filter scrutiny — worth investigating sender reputation and authentication setup.
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Amazon SES 2ESPs 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.
"Observed" pills mean we detected emails from these ESPs, but they don't appear in any SPF record we probed. They may still be properly authorized — sending infrastructure can live on subdomains we haven't seen yet, or use IP-listing instead of include: directives.
No additional ESPs authorized in the brand's SPF beyond the confirmed senders above.
Probed: americanexpress.com, bounce.member.americanexpress.com, mail.customercommunitycomms.americanexpress.com, bounce.e-response.americanexpress.com, bounce.notificationmycredit-guide.americanexpress.com, welcome.americanexpress.com, member.americanexpress.com, customercommunitycomms.americanexpress.com, e-response.americanexpress.com, notificationmycredit-guide.americanexpress.com, extmta1ipc2.americanexpress.com, extmta2ipc1.americanexpress.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 | 97.4% |
| promotions | 1 | 2.6% |
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 | 2 | 100.0% | 0.0% | 0.0% | |
| Salesforce MC | 30 | 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 americanexpress.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 136.147.130.157 | mta2.member.americanexpress.com |
12 | 8 | Check → |
| 136.147.130.158 | mta3.member.americanexpress.com |
7 | 1 | Check → |
| 136.147.130.159 | cb159.mta.exacttarget.com |
6 | 2 | Check → |
| 136.147.130.156 | mta.member.americanexpress.com |
6 | 1 | Check → |
| 139.71.11.9 | extmta1ipc2.americanexpress.com |
3 | — | Check → |
| 139.71.11.10 | extmta2ipc2.americanexpress.com |
2 | — | Check → |
| 139.71.106.170 | extmta2ipc1.americanexpress.com |
1 | — | Check → |
| 139.71.106.169 | extmta1ipc1.americanexpress.com |
1 | — | Check → |
| 54.240.8.86 | a8-86.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.48.91 | a48-91.smtp-out.amazonses.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
member.americanexpress.com | Salesforce MC 30 | 🐢 4/12 slow (avg 4 min 44 sec, peak 8 min 3 sec) |
welcome.americanexpress.com | SparkPost 7 | |
customercommunitycomms.americanexpress.com | Amazon SES 2 | |
notificationmycredit-guide.americanexpress.com | Salesforce MC 2 | |
e-response.americanexpress.com | Salesforce MC 1 |
