[ Setup article ]

How to Setup SPF for Mimecast?

1 min readBy Team EA

The Sender Policy Framework (SPF) is an email authentication system that detects forged sender addresses while the email is being delivered. SPF, on the other hand, is confined to detecting a forged sender claim in the email’s envelope, which is used when it bounces.

The setup process for Mimecast is fairly simple and similar to others. Follow the next few steps :

  • If you don’t have an existing SPF record, publish the following SPF record in your domain’s DNS:  v=spf1 include:_netblocks.mimecast.com ~all
  • If you have an existing SPF record, you will have to modify it by adding the record as follows :

 include:_netblocks.mimecast.com ~all

After you are done setting up SPF for Mimecast, use our free SPF validator tool to verify your records. 

[ SPF guide ]

Part of the Knowledge BaseSending-service implementation guides · 365 guides

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

[ Keep reading ]

All posts