amazon.com

Live email deliverability and anti-spoofing audit. Every value below was read from public DNS at the moment this page was generated.

Findings

• mx redundancy

  Only one mail exchanger is published, so there is no failover.

  amazon-smtp.amazon.com

  Fix: Add a secondary MX at a higher priority number.

• dkim

  No DKIM key found at any common selector. Either DKIM is not configured, or it uses a custom selector we cannot discover from DNS alone.

  Fix: Enable DKIM signing at your mail provider and publish the selector they give you.

• mta sts

  No MTA-STS policy, so inbound mail can be downgraded to an unencrypted connection.

  Fix: Publish _mta-sts.amazon.com and host a policy at https://mta-sts.amazon.com/.well-known/mta-sts.txt.

• mx

  1 mail exchanger published.

  5 amazon-smtp.amazon.com

• spf

  SPF is published and enforcing.

  v=spf1 include:spf1.amazon.com include:spf2.amazon.com include:amazonses.com -all

• dmarc

  DMARC is enforcing with p=quarantine.

  v=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.com

• bimi

  BIMI is published; supporting clients can show your logo.

  v=BIMI1;l=https://d3frv9g52qce38.cloudfront.net/amazondefault/order_1424920778_logo.svg;a=https://d3frv9g52qce38.cloudfront.net/amazondefault/amazon_web_services_inc_2026.pem

Records

curl "https://mailgrade.dev/v1/domain?domain=amazon.com"

Check another domain