Opens in a new tab

include:_netblocks.mimecast.com — Mimecast’s SPF includes, region by region

When outbound mail relays through Mimecast, your SPF record needs Mimecast’s include for your region — eu._netblocks.mimecast.com, us._netblocks.mimecast.com and so on. The global _netblocks.mimecast.com includes every region, which costs nine lookups on its own; Mimecast says to use the regional one. Mimecast also says its entry “must be the first one listed”.

v=spf1 include:eu._netblocks.mimecast.com ~all
Belongs toMimecast Email Security
Needed on your domain?Yes — mail from it uses your domain as the envelope sender, so SPF checks this record

What it costs, and is it in your record?

We measure include:_netblocks.mimecast.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Mimecast’s is there and what it costs.

What it covers

Outbound mail relayed through the Mimecast Email Security Cloud Gateway. Mimecast Email Security Cloud Integrated uses its own names, such as spf.us-1.a.mimecastprotect.com.

Do you need it?

Yes, when your outbound mail goes through Mimecast: the include is what allows Mimecast to send mail for your domain.

Moving Microsoft 365’s outbound mail to Mimecast, Mimecast’s guide replaces include:spf.protection.outlook.com with its own once all outbound mail routes through it; both can stay while the two run side by side.

Its other forms

IncludeFor
eu._netblocks.mimecast.comEurope, except Germany.
de._netblocks.mimecast.comGermany.
us._netblocks.mimecast.comUSA.
usb._netblocks.mimecast.comUSA, USB grid.
ca._netblocks.mimecast.comCanada.
za._netblocks.mimecast.comSouth Africa.
au._netblocks.mimecast.comAustralia.
_extnetblocks.mimecast.com (eu., us. …)Mail Mimecast sends for domains not internal to the account, such as with address rewriting.
spf.<region>-1.a.mimecastprotect.comMimecast Email Security Cloud Integrated — us-1, uk-1, de-1, ca-1, au-1.

Common mistakes

  • Keeping mx in the record once MX points to Mimecast: each Mimecast inbound host has more addresses than SPF allows, and the check fails. Remove mx.
  • je._netblocks.mimecast.com (Offshore) and the old uspcom name: Mimecast documents them, but they do not exist in DNS — an include of either fails SPF.
  • Copying Mimecast’s “strict” example literally: it prints –all with a dash that is not a hyphen, which breaks the record.
  • Mimecast listed twice — remove older Mimecast entries.

Questions

Is there a UK include?

No — uk._netblocks.mimecast.com does not exist. Mimecast’s UK accounts use eu._netblocks.mimecast.com.

Sources

Checked on 26 September 2026 against these official sources:

Stay under 10 lookups without dropping a sender

Let us host your SPF record: you publish one include line, we flatten every service in it to their addresses and refresh it hourly, so however many there are they fit in a few lookups — and we tell you when a service changes its addresses. On the Personal plan and up.

Create a free account