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:spf.mailjet.com include:sendgrid.net include:servers.mcsv.net include:_spf.google.com include:_spf.salesforce.com include:4899159.spf01.hubspotemail.net ~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; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]Enforces 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://vmc.digicert.com/506b2123-e56f-4770-8fc8-218cd458db6c.svg; a=https://vmc.digicert.com/506b2123-e56f-4770-8fc8-218cd458db6c.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.