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.google.com include:sendgrid.net include:8867829.spf04.hubspotemail.net include:_spf.intacct.com include:_spf.atlassian.net include:_spf.hostedemail.com include:shops.shopify.com ~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=noneEnforces TLS for inbound mail and prevents downgrade attacks
MTA-STS is enforcing TLS.
v=STSv1;id=1601545867215;Receives reports about TLS delivery failures
TLS reporting is configured.
v=TLSRPTv1;rua=mailto:[email protected];Displays your verified brand logo in supporting inboxes
BIMI is published with caveats.
v=BIMI1; l=https://cookies.co/bimi/cookies_sf_llc_286863927.svg; a=https://cookies.co/bimi/cookies_sf_llc_286863927.pem;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.