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 mx include:spf.mailjet.com include:_spf.google.com ip4:159.135.238.185 ip4:143.55.227.12 include:mail.zendesk.com include:md02.com include:_spf.myorderbox.com include:_spf.emfwd.name-services.com MX ~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 enforced.
v=DMARC1;p=reject;sp=reject;pct=100;rua=mailto:[email protected],mailto:[email protected];ruf=mailto:[email protected],mailto:[email protected];ri=86400;aspf=s;adkim=s;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://bimi.trust-provider.com/3009536908/current/logo.svg; a=https://bimi.trust-provider.com/3009536908/current/cert.pemChecks 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.