A90/100

amazon.com

Name: amazon.com email authentication report
Creator: MailAuthWatch
License: https://creativecommons.org/publicdomain/zero/1.0/

Solid. A couple of things could still be tighter. 1 item below, ordered by how much inbox it is costing you. Measured 0s ago from public DNS in 88 ms.

SPF PASSDKIM 1024-BITDMARC QUARANTINEMX OK

Monitor this domain Re-run check

Fix these, in this order, or hand the list to your agent

ranked by impact

One DKIM key is 1024-bit.

Selector m1._domainkey is under 2048 bits, which some receivers already downgrade.

Do this: rotate to a 2048-bit key at the sending service.

Records found

SPF · TXT

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

DMARC · _dmarc.amazon.com

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

DKIM · 1 of 79 selectors

m1._domainkey · 1024-bit

MX · Custom / other

5 amazon-smtp.amazon.com

Fix this with your AI agent

AGENT-READY

A prompt built only from what was measured: the records as published, 1 task in order, exact record values and Amazon Route 53 commands, guardrails, and how to verify. Paste it into Claude, Cursor, Copilot or ChatGPT.

# Fix email authentication for amazon.com

You are working on the DNS and mail configuration for amazon.com.
Measured by MailAuthWatch on 17 Oct 2026 from public DNS. Grade A (90/100).
Report: https://www.mailauthwatch.com/check/amazon.com

## What is published right now (do not assume anything else)
- SPF (TXT amazon.com): v=spf1 include:spf1.amazon.com include:spf2.amazon.com include:amazonses.com -all   — valid, 4 of 10 lookups
- DMARC (TXT _dmarc.amazon.com): v=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.com
- DKIM: m1._domainkey (1024-bit)
- MX: amazon-smtp.amazon.com  → a custom mail host
- Nameservers: ns-1447.awsdns-52.org, ns-1707.awsdns-21.co.uk …  → records are managed in Amazon Route 53

## Tasks, in order of impact
…

# Fix email authentication for amazon.com

You are working on the DNS and mail configuration for amazon.com.
Measured by MailAuthWatch on 17 Oct 2026 from public DNS. Grade A (90/100).
Report: https://www.mailauthwatch.com/check/amazon.com

## What is published right now (do not assume anything else)
- SPF (TXT amazon.com): v=spf1 include:spf1.amazon.com include:spf2.amazon.com include:amazonses.com -all   — valid, 4 of 10 lookups
- DMARC (TXT _dmarc.amazon.com): v=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.com
- DKIM: m1._domainkey (1024-bit)
- MX: amazon-smtp.amazon.com  → a custom mail host
- Nameservers: ns-1447.awsdns-52.org, ns-1707.awsdns-21.co.uk …  → records are managed in Amazon Route 53

## Tasks, in order of impact
### 1. One DKIM key is 1024-bit.
Why: Selector m1._domainkey is under 2048 bits, which some receivers already downgrade. 
Rotate to a 2048-bit key at the sending service.

## Rules
- Publish exactly one SPF record; never add a second v=spf1 TXT.
- Do not remove any include: or ip4: you cannot account for; mail may depend on it.
- Do not set DMARC to p=reject in one step; stage through p=none → quarantine → reject.
- Show the planned DNS changes as a diff (record, old value, new value) before applying them.
- If you cannot access Amazon Route 53, stop and say exactly what access you need.

## Verify
  dig +short TXT amazon.com
  dig +short TXT _dmarc.amazon.com
Then open https://www.mailauthwatch.com/check/amazon.com?fresh=1 and confirm:
  the grade is unchanged and no new issues appear. Target grade: A.

## Report back
List each record you changed (name, type, old value, new value), what you verified, and anything you could not do.

Open in Claude Open in ChatGPT fix.md

Your agent, your DNS, your review. MailAuthWatch never changes records; it writes the plan and re-checks the result.

Grade history

Free checks keep nothing. Monitoring records every daily measurement and alerts you on change.

History goes back as far as your subscription.

SPF OK

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

DNS lookups: 4 of 10 allowed
Final mechanism: -all

OK No problems detected.

Include tree

4 / 10

amazon.com0

├─ include:spf2.amazon.com+2

│ └─ spf3.amazon.com

├─ include:spf1.amazon.com+1

└─ include:amazonses.com+1

DKIM OK

DKIM selectors cannot be listed from DNS, so 79 selectors used by common providers were probed.

Selector	Key	Record
`m1`	RSA 1024-bit Weak	`v=DKIM1;k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDAiSCfuVglLVcKGSFDAPmf1fg/bwnQkgxVkL…`

WarningDKIM selector "m1" uses a 1024-bit key. Rotate to 2048 bits.
NoteSelectors "zendesk1", "zendesk2" are published with an empty key (decommissioned). Harmless as long as nothing signs with them.

DMARC OK

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

Policy: p=quarantine
Applies to: 100% of failing mail
Aggregate reports: mailto:report@dmarc.amazon.com

NotePolicy is p=quarantine. p=reject is the strongest protection once you are confident all senders are aligned.

Mail exchange and extras

OK No problems detected.

MTA-STS: Not published optional: enforces TLS for inbound mail
TLS-RPT: Not published
BIMI: OK 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 the grade is calculated

Score 90/100. SPF present and valid. SPF ends with -all. DKIM found (1 selector). DMARC present and valid. DMARC policy is quarantine. DMARC aggregate reporting enabled. SPF contributes up to 35 points, DKIM up to 25, DMARC up to 40 (policy strength and reporting). Any critical issue caps the grade at C. Lookups that failed are shown as "not measured" and never counted as missing.

Check another domain:

Other recently graded domains

Public checks from the last few days. Every report is re-measured from DNS when opened.

live

DomainSPFDKIMDMARCGrade

github.com10 lookups2048-bitp=quarantineA gmail.com1 lookupsnot foundp=noneC microsoftonline.com6 lookupsnot foundp=rejectB salesforce.com4 lookups2048-bitp=rejectA mailauthwatch.com1 lookups1024-bitp=rejectA google.com1 lookupsnot foundp=rejectB notion.so0 lookupsnot foundp=quarantineC gandi.net2 lookupsnot foundp=noneC mailship.com1 lookupsnot foundmissingD azure.com2 lookupsnot foundp=rejectB facebook.com1 lookupsnot foundp=rejectB bing.com1 lookupsnot foundp=rejectB