inbound-smtp.<region>.amazonaws.com, at 10, receives mail for Amazon SES’s email receiving in the region where the receipt rules live — and for Amazon WorkMail, which uses the same hosts. SES Mail Manager endpoints have their own names under mail-manager-smtp.amazonaws.com.
| What it is | Inbound mail for an app |
| MX records | 10 inbound-smtp.<region>.amazonaws.com |
| SPF | include:amazonses.com |
Does your domain use Amazon SES?
Enter a domain: we read its MX records as a sending server does, name whose each host is, and say whether Amazon SES’s are all there — and what else is.
The MX records
What Amazon SES asks for, with your own values in place of the placeholders:
example.com. MX 10 inbound-smtp.<region>.amazonaws.com.
Worth knowing
feedback-smtp.<region>.amazonses.com is a different thing: the MX of a custom MAIL FROM subdomain, where bounces and complaints about mail you sent come back. It is not an inbox.
SES receiving is not an IMAP or POP mailbox: it hands mail to S3, Lambda or SNS.
Sending mail through Amazon SES too? Its SPF, DKIM and DMARC records, and a check of all three.
Sources
Checked on 27 September 2026 against these official sources:
- Publishing an MX record for Amazon SES email receiving — docs.aws.amazon.com
- Amazon Simple Email Service endpoints and quotas — docs.aws.amazon.com
- Using a custom MAIL FROM domain — docs.aws.amazon.com
- Ingress endpoints — docs.aws.amazon.com