amazon.com
71/100
Mail provider: Unknown
| Check | Details | |
|---|---|---|
| MX | ✔ | amazon-smtp.amazon.com |
| SPF | ✔ | v=spf1 include:spf1.amazon.com include:spf2.amazon.com include:amazonses.com -all (4 lookups) |
| DKIM | ✖ | No DKIM key found on common selectors (a custom selector may exist - check a sent email's DKIM-Signature: s= header). |
| DMARC | ✔ | v=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.com |
| MTA-STS | ⚠ | Not set (optional; enforces TLS for mail sent to you) |
| TLS-RPT | ⚠ | Not set (optional; reports TLS delivery failures) |
| BIMI | ✔ | v=BIMI1;l=https://d3frv9g52qce38.cloudfront.net/amazondefault/order_1424920778_logo.svg;a=https://d3frv9g52qce38.cloudfront.net/amazondefault/amazon_web_services_inc_2026.pem |
How to fix it
- DKIM — Turn on DKIM signing in your email provider and publish the TXT/CNAME it gives you
(record value comes from your provider's admin panel)
DNS changes can take up to 24–48 hours. Re-run the check afterwards.
Want it fixed for you? I set up SPF, DKIM and DMARC without breaking your other senders,
with a before/after report.
Get it fixed on Fiverr
Get it fixed on Fiverr
Prefer to do it yourself? Get the step-by-step Fix Kit ($15) – 19-page guide, checklist, 20+ providers.