Fastmail receives mail at in1-smtp.messagingengine.com (10) and in2-smtp.messagingengine.com (20) — and says these should be the only two MX records. Subdomains use a wildcard MX with the same values.
| What it is | Mailbox provider |
| MX records | 10 in1-smtp.messagingengine.com20 in2-smtp.messagingengine.com |
| SPF | include:spf.messagingengine.com |
| DKIM selector | fm1, fm2, fm3 |
| TTL | 1 hour |
| Taking effect | Usually minutes, up to a day |
Does your domain use Fastmail?
Enter a domain: we read its MX records as a sending server does, name whose each host is, and say whether Fastmail’s are all there — and what else is.
The MX records
What Fastmail asks for:
example.com. MX 10 in1-smtp.messagingengine.com.
example.com. MX 20 in2-smtp.messagingengine.com.
Older names
These still receive mail, though Fastmail now documents the records above:
in1.smtp.messagingengine.comin2.smtp.messagingengine.com
Worth knowing
Fastmail changed the names from in1.smtp to in1-smtp in 2012, so the certificate matches for encrypted delivery; it kept the old ones working.
Common mistakes
- Any MX record beside the two.
- A trailing dot: try without one first, and add it if the DNS host appends anything.
What changed
- 6 January 2012 — Default names changed from in1.smtp to in1-smtp.messagingengine.com.
Sources
Checked on 27 September 2026 against these official sources:
- Setting up your domain: MX only — fastmail.help
- Manual DNS configuration — fastmail.help
- Change of default MX records for domains — fastmail.com