Email senders
Fastmail DMARC setup: SPF and three DKIM records
Set up Fastmail authentication on your own domain, publish all three DKIM CNAMEs and check reports before enforcing a DMARC policy.
SPF include for Fastmail
include:spf.messagingengine.com
Add this to the SPF record you already have. A domain must publish only one SPF record, so never create a second one.
- DNS lookups it uses
- 1 of 10
- Needed in your SPF record
- Yes
- Last checked in DNS
- 2026-11-11
DKIM for Fastmail
- Selectors
- fm1 fm2 fm3
- How to enable it
- Publish all three CNAME records, fm1._domainkey, fm2._domainkey and fm3._domainkey, using the targets for your domain in Settings > Domains. Fastmail hosts the public keys.
Fastmail can sign with your domain once you set it up
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Fastmail’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- Fastmail does not document this.
Sending ranges of Fastmail
Use these to recognize Fastmail in your reports. They change over time, so do not copy them into your SPF record.
- 103.168.172.0/24
- 66.111.4.0/24
- 103.168.172.128/27
- 202.12.124.128/27
- 204.75.18.128/27
Updated 2026-11-15
Does your domain authorize Fastmail?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Fastmail documentation
- Fastmail: Manual DNS configuration
- checked 2026-11-09
- Fastmail: Custom domains
- checked 2026-11-09
- Fastmail: Domain setup wizard
- checked 2026-11-09
- Fastmail: Setting up your domain, MX only
- checked 2026-11-09
How it authenticates
Fastmail DMARC setup on a custom domain combines SPF and DKIM authentication with a separate policy in DNS. An account administrator manages the domain under Settings > Domains. When DNS stays elsewhere, publish the records with that DNS provider.
Fastmail documents three DKIM CNAMEs, with selectors fm1, fm2 and fm3. Add all three. They point to keys hosted by Fastmail, with your domain in each target. For example, the first target for example.com is fm1.example.com.dkim.fmhosted.com. Copy your actual values from the domain instructions; do not substitute another customer's domain.
The documented SPF include authorizes Fastmail's sending servers. Add it to the SPF record you already have, keeping other legitimate senders. A second SPF record causes an error. Use the SPF checker to check the combined result.
What to watch for
Moving nameservers to Fastmail affects more than outgoing mail. Its wizard offers an MX-only route for domains with a website. Keep existing website and service records when choosing how to connect the domain.
Fastmail's starter DMARC value uses p=none. If you already have a DMARC record, keep one record and preserve its policy and report addresses. For a new deployment, add a rua address you monitor, then check that Fastmail mail passes with aligned authentication before tightening the policy. The starter value without rua requests no aggregate reports.