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:mxsspf.sendpulse.com include:mail.registrar.eu include:mail.zendesk.com include:spf.zoho.eu include:eu.transmail.net include:spf.zohomail360.eu a mx include:_spf.google.com ip4:107.181.175.20 ip4:193.111.62.160 ip4:162.247.154.150 ip4:62.192.154.11 ip4:45.83.195.254 ip4:193.111.61.142 ~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; sp=quarantine; ruf=mailto:[email protected]; rua=mailto:[email protected]; rf=afrf; pct=100; aspf=r; adkim=r; ri=86400Enforces 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
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.