create_domain
Register a sending domain, create its Amazon SES identity, and return the DNS records to publish.
›Add mail.acme.com as a sending domain in eu-west-1 and show me the DNS records as a table.
What it does
Creating a domain provisions the SES identity in the region you pick and returns the full DNS set you need to publish: three DKIM CNAMEs, the MAIL FROM MX and SPF records, and a DMARC record. Your assistant will normally render these as a table you can copy into Cloudflare, Route 53 or whatever hosts your zone.
The MAIL FROM subdomain matters more than people expect. Setting it moves the bounce path onto your own domain so SPF aligns for DMARC, instead of leaving the envelope sender on an Amazon-owned domain. Raechly configures it by default rather than treating it as an advanced option.
Sending stays blocked until the identity verifies. That is deliberate: an unverified identity that "sort of" sends is how domains get burned in week one.
Parameters
| Name | Type | Notes |
|---|---|---|
| domain * | string | Use a subdomain or a dedicated domain — never your primary corporate domain. |
| ses_region | string | AWS region for the identity. Defaults to us-east-1. |
* required · Maps to POST /api/domains
What comes back
The domain record plus `dns_records[]` — DKIM CNAMEs, MAIL FROM MX and SPF, DMARC.
The thing people get wrong
Never register your primary corporate domain. Cold volume belongs on a dedicated domain so a reputation hit never touches the mail your business actually depends on.
Use it with
More domains tools
See all 22 tools and the connection string on the MCP server page.