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:_spfcf1.yosh.ai include:_spfcf2.yosh.ai include:_spfcf3.yosh.ai include:_spfcf4.yosh.ai include:_spfcf5.yosh.ai include:_spfcf6.yosh.ai include:_spf.google.com include:spf.mailjet.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 enforced.
v=DMARC1; p=quarantine; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]; fo=1; adkim=s; aspf=s; pct=100;Enforces TLS for inbound mail and prevents downgrade attacks
MTA-STS is published but not enforcing.
v=STSv1;id=1608661149679;Receives reports about TLS delivery failures
TLS reporting is configured.
v=TLSRPTv1;rua=mailto:[email protected];Displays your verified brand logo in supporting inboxes
No BIMI record. No brand logo is published for inboxes.
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.