5 sending services found from public records checked 2026-10-12 01:24 UTC (629 lookups in 0.0 s over Google DNS over HTTPS).
Mimecast stands in front of the domain's mail as a security gateway, so the mailbox provider is not visible from MX.
Four other services are set up to send as the domain: one commerce and apps (Docebo), one support and CRM (Freshdesk), one mailbox (Microsoft 365), one transactional (SendGrid).
DMARC reports go to Mimecast DMARC Analyzer.
Not checked: the website (turned off), DKIM selectors past the first 27 on two subdomains, and the crt.sh certificate log (read only with --ct).
Some receivers already treat 1024-bit RSA keys as weak. Rotate to 2048-bit.
Its documented setup needs it and the map shows it missing: no key at selector1._domainkey or selector2._domainkey, names with no TXT record; this zone gives that answer for every name that does not exist.
Inferred from the MX records: a security gateway filters incoming mail and hands it on to the server that holds the mailboxes, and MX records do not say which server that is.
MX: eu-smtp-inbound-1.mimecast.com, eu-smtp-inbound-2.mimecast.com
MX
SPF
SPF: include:docebosaas.com
SPF
SPF range: ip4:3.120.181.200/29
SPF range
SPF: include:spf.protection.outlook.com
setup incomplete: DKIM missing
SPF
Verification token
Autodiscover CNAME
setup incomplete: SPF present, DKIM missing, MX not used (optional, MX at mills-reeve.com), bounce CNAME not needed
DKIM keys: s1, s2 (1024 and 2048 bit, by CNAME)
setup complete
DKIM keys
setup complete: DKIM present, bounce CNAME not used (optional, CNAME at 25 labels under mills-reeve.com), SPF not needed, tracking CNAME not used (optional, CNAME at 25 labels under mills-reeve.com)
Mimecast DMARC Analyzer
629 lookups at 3 names