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.protection.outlook.com +ip4:203.18.108.164 +ip4:113.52.5.0/27 +ip4:103.182.173.0/24 +include:mandrillapp.com +ip4:203.18.108.163 +include:amazonses.com +include:maildelivery.com.au +include:rec-marketing.dc2.pageuppeople.com +ip4:54.153.131.110 +include:spf-0086a301.pphosted.com +ip4:13.73.207.31 +ip4:20.227.98.96 ~allCryptographically signs outgoing mail (best-effort selector probe)
DKIM key published for 4 known selectors.
Tells receivers what to do with mail that fails SPF and DKIM
DMARC is published but not fully enforcing.
v=DMARC1; p=none; rua=mailto:[email protected], mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected], mailto:[email protected],mailto:[email protected]; fo=0; adkim=r; aspf=r; pct=100; rf=afrf; ri=86400Enforces TLS for inbound mail and prevents downgrade attacks
MTA-STS is enforcing TLS.
v=STSv1; id=20260604T020000Z;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.