amazon.com

amazon.com · Last checked 2026-10-04 02:02 UTC

amazon.com

Excellent, with 1 thing to fix

amazon.com scored 92/100 (grade A). The main issue is DKIM key revoked. Detected senders: Amazon SES.

Checked 2026-10-04 02:02 UTC · fresh check

2 passed1 needs attention0 failing5 for informationDetected senders: Amazon SES

All checks

MXCan servers find your inbox?Only one MX hostInfo
  • Info: Only one MX host

    All mail for amazon.com goes to amazon-smtp.amazon.com. Most hosted providers make that one name highly available; if you run your own server, consider a backup MX.

SPFWho may send as you?No issues foundPass

Nothing to report.

DKIMAre your emails signed?DKIM key revokedNeeds attention
  • Warning: DKIM key revoked

    zendesk1, zendesk2 publishes an empty p= tag, so any mail still signed with that selector fails DKIM. That is correct after a key rotation; otherwise publish the current key or stop signing with this selector.

DMARCWhat happens to fakes?DMARC policy is quarantine; consider rejectInfo
  • Info: DMARC policy is quarantine; consider reject

    Failing mail goes to spam rather than being refused. When reports show no legitimate failures, reject gives the strongest protection.

    How to fix this
AlignmentDoes it match your From?SPF alignment depends on a custom Return-PathInfo
  • Info: SPF alignment depends on a custom Return-Path

    This is a heuristic. Your SPF record only authorizes third-party senders (amazonses.com). By default they bounce from their own Return-Path domain, and SPF then passes for that domain, not amazon.com. Even relaxed alignment needs the Return-Path's organizational domain to be amazon.com, so set up a custom Return-Path (bounce) domain under amazon.com with each provider, and sign with DKIM as amazon.com.

BIMICan inboxes show your logo?No issues foundPass

Nothing to report.

MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
  • Info: No MTA-STS record

    No MTA-STS record at _mta-sts.amazon.com. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.

    How to fix this
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
  • Info: No TLS-RPT record

    No TLS reporting record at _smtp._tls.amazon.com. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

How to fix it

Strengthen the DMARC policyTXT

Rejects mail that fails DMARC, the strongest protection against spoofing.

TypeTXT
Name / Host
_dmarc.amazon.com

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=reject; rua=mailto:report@dmarc.amazon.com; adkim=r; aspf=r
Replaces
v=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.com

Publish the MTA-STS recordTXT

Tells sending servers that amazon.com publishes an MTA-STS policy at https://mta-sts.amazon.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT
Name / Host
_mta-sts.amazon.com

Some DNS providers want just “_mta-sts” here.

Value
v=STSv1; id=202610040202

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.amazon.com. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location
https://mta-sts.amazon.com/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: amazon-smtp.amazon.com
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to amazon.com, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.

Applies to: _smtp._tls.amazon.com

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@amazon.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.amazon.com with the value v=TLSRPTv1; rua=mailto:<that address>.