fm1, fm2 and fm3 are Fastmail’s DKIM selectors: three CNAMEs to fmhosted.com, behind which Fastmail rotates the keys itself. It will not sign with your domain until all three are in place.
| Whose | Fastmail — mailbox provider |
| Selector | fm1, fm2, fm3 |
| Published as | Three CNAMEs, to fm1.<your domain>.dkim.fmhosted.com and its fm2 and fm3 siblings |
| Key | The keys behind the CNAMEs are 2048-bit |
| Rotation | Automatic |
| Before you set it up | Fastmail always signs with its own messagingengine.com as well, and with your domain once the CNAMEs verify |
| Where to find it | Settings → Domains → the domain |
| Can it go? | Once the domain’s mail no longer goes through Fastmail. Domains hosted there before 2018 may still have mesmtp, which is deprecated. |
Is Fastmail’s key on your domain?
Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Fastmail’s key under fm1 and fm2 and fm3 and mesmtp, check it, and name every other key the domain publishes.
The records
What Fastmail asks you to publish, with its own values in place of the placeholders:
fm1._domainkey.example.com CNAME fm1.example.com.dkim.fmhosted.com
fm2._domainkey.example.com CNAME fm2.example.com.dkim.fmhosted.com
fm3._domainkey.example.com CNAME fm3.example.com.dkim.fmhosted.com
Common mistakes
- Only one or two of the three CNAMEs.
- Cloudflare’s proxy switched on — it must be DNS only.
Sources
Checked on 27 September 2026 against these official sources:
- Manual DNS configuration — fastmail.help
- Why do I need DKIM? — fastmail.help
- DKIM signing outgoing email with From address domain — fastmail.com