Last scanned 2h ago · Mar 30, 2026, 10:53 PM
Only DMARC is configured. Your domain needs SPF, DKIM, and DMARC working together to prevent spoofing.
First scan · Mar 30, 2026, 10:53 PM
Detected Record
v=DMARC1; p=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1
Policy
quarantine
Percentage
100%
Aggregate Reporting
mailto:rua@dmarc.microsoft
Forensic Reporting
mailto:ruf@dmarc.microsoft
DKIM Alignment
relaxed
SPF Alignment
relaxed
Consider escalating to p=reject once compliance is consistently above 98%.
Publish an SPF record listing your authorized email senders (e.g. v=spf1 include:_spf.google.com ~all).
Ensure your email provider has published DKIM keys. If using a custom selector, DKIM may still be active.
Detected Record
v=STSv1; id=20180321T030303;
Policy ID
20180321T030303
Policy File
accessible
Mode
testing
Max Age
604800s (7d)
MX Match
policy MX does not match actual MX
Switch MTA-STS policy from testing to enforce once you have verified TLS works for all senders.
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.