Email authentication
The basics are in place but can be hardened.
Authorizes which servers may send mail for the domain
SPF is published but could be tightened.
v=spf1 include:userinclude.dme3ds1.com include:spf.mandrillapp.com include:_spf.hushmail.com include:servers.mcsv.net include:sendgrid.net include:_spf.elasticemail.com include:_spf.google.com -allCryptographically signs outgoing mail (best-effort selector probe)
DKIM key published for 5 known selectors.
Tells receivers what to do with mail that fails SPF and DKIM
DMARC is enforced.
v=DMARC1;p=quarantine;pct=100;rua=mailto:[email protected],mailto:[email protected],mailto:[email protected];ruf=mailto:[email protected],mailto:[email protected];fo=1Enforces TLS for inbound mail and prevents downgrade attacks
No MTA-STS policy. Inbound mail can be delivered without TLS.
Receives reports about TLS delivery failures
No TLS-RPT record. You get no reports about failed TLS delivery.
Displays your verified brand logo in supporting inboxes
BIMI is published.
v=BIMI1;l=https://awr.org/media/icon-turquoise-awrlabs.svg;a=Checks query live DNS over Cloudflare and the public MTA-STS policy endpoint. DKIM selectors cannot be listed from DNS, so DKIM detection probes common provider selectors only.