Opens in a new tab

in1-smtp.messagingengine.com: Fastmail’s MX records

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 isMailbox provider
MX records10 in1-smtp.messagingengine.com
20 in2-smtp.messagingengine.com
SPFinclude:spf.messagingengine.com
DKIM selectorfm1, fm2, fm3
TTL1 hour
Taking effectUsually 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.com
  • in2.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:

Know when your MX records change

Add your domain and we check its DNS on a schedule and email you when its records change — so a provider switch left half done, or an MX nobody meant to add, does not go unnoticed. Free for your first domain.

Create a free account