MX records for mimecast.com
Live MX lookup for mimecast.com: 2 mail hosts, run by Mimecast.
try:
- mail hosts
- service-alpha-inbound-a.mimecast.com, service-alpha-inbound-b.mimecast.com
- provider
- mimecast
- spf record
- v=spf1 redirect=aojpw1q8._spf._d.mim.ec
- dmarc policy
- reject
- dmarc record
- v=DMARC1; p=reject; rua=mailto:[email protected],mailto:74e31d82-60cd-440c-ae8a-75b8a5c2ad94@rep.uk.mimecastdmarcanalyzer.com; ruf=mailto:[email protected]; pct=100; fo=1;
- disposable domain
- no
- free consumer provider
- no
Mail servers for mimecast.com
mimecast.com publishes 2 MX records. Senders deliver to the lowest-priority host first, service-alpha-inbound-a.mimecast.com, and fall back down the list if it does not answer.
Who runs the mail
The hosts match the pattern of Mimecast. Mimecast sits in front of the real mail servers as a filtering gateway. It accepts most recipients at the handshake and rejects later, which makes catch-all the expected answer from a mailbox probe.
What this means for verification
An address at mimecast.com passes the free checks (syntax, MX, lists), so the API goes on to the mailbox-level SMTP handshake, which ends before any message is sent. The result is deliverable, risky, or undeliverable with a reason field that names the evidence.
More checks for mimecast.com
checked 2026-09-03 · sources: live-dns 2026-09-03 · disposable-domains 2026-09-02 · free-provider-domains 2026-09-02 · mx-provider-patterns 2026-09-03 · rdap-registration 2026-09-03
Need this at scale?
The Spaw API runs the same checks plus mailbox-level SMTP verification, batch and bulk endpoints, and list monitoring — 10 free lookups a month, no card required.