Mailgun receives mail at mxa.mailgun.org and mxb.mailgun.org, both at 10 — mxa and mxb.eu.mailgun.org in its EU region — to pass it to your app through Routes or Forwards. It is usually on a sending subdomain such as mail.example.com, not the domain your people use.
| What it is | Inbound mail for an app |
| MX records | 10 mxa.mailgun.org10 mxb.mailgun.org |
| SPF | include:mailgun.org |
Does your domain use Mailgun?
Enter a domain: we read its MX records as a sending server does, name whose each host is, and say whether Mailgun’s are all there — and what else is.
The MX records
What Mailgun asks for — or one of the other sets below, depending on where the account is or how it was set up:
example.com. MX 10 mxa.mailgun.org.
example.com. MX 10 mxb.mailgun.org.
Other sets
| Where | MX records |
|---|---|
| EU region | 10 mxa.eu.mailgun.org10 mxb.eu.mailgun.org |
Worth knowing
Mailgun recommends the MX on a sending subdomain even if nothing is received there: some receivers check that the sender’s domain has an MX before accepting mail from it.
Common mistakes
- Mailgun’s MX added to the root domain beside the mailbox provider’s — mail is split between them.
Sending mail through Mailgun too? Its SPF, DKIM and DMARC records, and a check of all three.
Sources
Checked on 27 September 2026 against these official sources:
- Getting started Sending Email — documentation.mailgun.com
- Domain Verification Setup Guide — help.mailgun.com
- Why did I receive the error Sender Verify Failed or some variation thereof — help.mailgun.com