include:spf.messagingengine.com is Fastmail’s SPF include — messagingengine.com is the domain of Fastmail’s mail servers. Fastmail’s suggested record ends with ?all, neutral, rather than the usual ~all: with it, SPF never fails, so a DMARC policy on your domain relies on DKIM.
v=spf1 include:spf.messagingengine.com ?all
| Belongs to | Fastmail |
| Needed on your domain? | Yes — mail from it uses your domain as the envelope sender, so SPF checks this record |
| Fastmail’s ending | ?all (neutral) |
What it costs, and is it in your record?
We measure include:spf.messagingengine.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Fastmail’s is there and what it costs.
What it covers
All mail Fastmail sends for your domain, whichever data centre your account is in — data residency changes the MX hosts, not the SPF include.
Do you need it?
Yes: it “Allows receivers to know you send your mail via Fastmail”. Fastmail’s mail carries your own address as the envelope sender, so SPF checks your record.
Subdomains you send from need their own: “If you intend to send mail from subdomain addresses, then you’ll also need to add DKIM and SPF for your subdomain as well.”
Common mistakes
- Two records starting with v=spf1 — “will cause an issue with SPF detection”. Combine them.
- Counting includes rather than lookups: Fastmail says “up to 10 SPF records”, but lookups nested inside includes count too.
Questions
Should I keep ?all?
It is Fastmail’s default, which lets other systems send from your addresses without failing SPF. If Fastmail and the services in your record are your only senders, ~all or -all tells receivers more — and DMARC still relies on DKIM either way.
Sources
Checked on 26 September 2026 against these official sources:
- Manual DNS configuration — fastmail.help
- Choosing your data residency — fastmail.help
- Dec 9: Email authentication — fastmail.com