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:146469162.spf05.hubspotemail.net include:_spf.salesforce.com include:_spf.google.com include:spf.mandrillapp.com include:stspg-customer.com include:_spf.atlassian.net ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26 ip4:37.188.97.188/32 ip4:185.28.196.0/22 ip4:192.28.128.0/18 ip4:103.237.104.0/22 ip4:130.248.172.0/24 ip4:130.248.173.0/24 -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=reject;adkim=s;aspf=s;sp=reject;rua=mailto:[email protected];ruf=mailto:[email protected];fo=1Enforces TLS for inbound mail and prevents downgrade attacks
MTA-STS is enforcing TLS.
v=STSv1; id=2024020502Receives 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.