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 a mx include:_spf.google.com include:spf.mandrillapp.com include:fdspfeuc.freshemail.io include:spf.smartemailing.cz ~allCryptographically signs outgoing mail (best-effort selector probe)
DKIM key published for 2 known selectors.
Tells receivers what to do with mail that fails SPF and DKIM
DMARC is published but not fully enforcing.
v=DMARC1; p=none; rua=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 with caveats.
v=BIMI1; l=https://storage.googleapis.com/patron-blog-production-gcs/patron_logo_email_b1f2cd725e/patron_logo_email_b1f2cd725e.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.