Last scanned 2h ago · Mar 30, 2026, 10:53 PM
Good progress. SPF and DKIM are in place. DKIM needs attention to complete your protection.
First scan · Mar 30, 2026, 10:53 PM
Detected Record
v=DMARC1; p=quarantine; sp=none; pct=100; rua=mailto:aws-marketing-email-dmarc-rua-reports@dmarc.amazonaws.com; ruf=mailto:aws-marketing-email-dmarc-ruf-reports@dmarc.amazonaws.com
Policy
quarantine
Percentage
100%
Aggregate Reporting
mailto:aws-marketing-email-dmarc-rua-reports@dmarc.amazonaws.com
Forensic Reporting
mailto:aws-marketing-email-dmarc-ruf-reports@dmarc.amazonaws.com
Subdomain Policy
none
DKIM Alignment
relaxed
SPF Alignment
relaxed
Consider escalating to p=reject once compliance is consistently above 98%.
Detected Record
v=spf1 include:amazon.com ~all
All Mechanism
~all (soft fail)
DNS Lookups
2/10
Record Length
30 bytes
Consider tightening to -all for stricter enforcement alongside your DMARC policy.
Ensure your email provider has published DKIM keys. If using a custom selector, DKIM may still be active.
Publish an MTA-STS TXT record and host a policy file at https://mta-sts.yourdomain/.well-known/mta-sts.txt.
Publish a TLS-RPT record to receive reports when sending servers fail to establish encrypted connections.
Publish a BIMI record with your brand SVG logo. Requires DMARC at p=quarantine or p=reject with pct=100.