Amazon WorkMail receives mail at inbound-smtp.<region>.amazonaws.com at priority 10, in N. Virginia, Oregon or Ireland. AWS is ending WorkMail: no new customers from 30 April 2026, and support ends on 31 March 2027.
| What it is | Mailbox provider |
| MX records | 10 inbound-smtp.<region>.amazonaws.com |
| SPF | include:amazonses.com |
| DKIM selector | <token>, three of them |
| TTL | 1 hour |
| Taking effect | Up to 48 hours |
Does your domain use Amazon WorkMail?
Enter a domain: we read its MX records as a sending server does, name whose each host is, and say whether Amazon WorkMail’s are all there — and what else is.
The MX records
What Amazon WorkMail asks for, with your own values in place of the placeholders — or one of the other sets below, depending on where the account is or how it was set up:
example.com. MX 10 inbound-smtp.<region>.amazonaws.com.
Other sets
| Where | MX records |
|---|---|
| N. Virginia | 10 inbound-smtp.us-east-1.amazonaws.com |
| Oregon | 10 inbound-smtp.us-west-2.amazonaws.com |
| Ireland | 10 inbound-smtp.eu-west-1.amazonaws.com |
Worth knowing
The same host receives mail for Amazon SES’s inbound email; the record alone does not say which of the two uses it.
Common mistakes
- Other MX records beside it: AWS says WorkMail should be the only entry and have the lowest number.
What changed
- 30 April 2026 — WorkMail stopped accepting new customers.
- 31 March 2027 — WorkMail ends; its console and resources go.
Sources
Checked on 27 September 2026 against these official sources:
- Amazon WorkMail end of support — docs.aws.amazon.com
- Verifying domains — docs.aws.amazon.com
- Adding a domain — docs.aws.amazon.com