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=reject; fo=1; rf=afrf; ri=86400; rua=mailto:verisign@rua.agari.com,mailto:mailreports@verisign.com; ruf=mailto:verisign@ruf.agari.com,mailto:mailauthfail@verisign.com
Policy
reject
Aggregate Reporting
mailto:verisign@rua.agari.com,mailto:mailreports@verisign.com
Forensic Reporting
mailto:verisign@ruf.agari.com,mailto:mailauthfail@verisign.com
DKIM Alignment
relaxed
SPF Alignment
relaxed
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.
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.