Domains
Verify a domain to send live email from it.
Live keys can only send from domains your organization has verified. Domains belong to the organization and are shared by all of its projects.
Adding a domain
Add the domain in the dashboard (Domains) or through the API, then publish the DNS records it returns at your DNS provider:
const { : , } = await ..({ : "acme.com" });
for (const of ?. ?? []) {
.(., ., .);
}| Purpose | Type | Name | Value |
|---|---|---|---|
| DKIM (three records) | CNAME | <token>._domainkey.example.com | <token>.dkim.amazonses.com |
| MAIL FROM | MX | send.example.com | feedback-smtp.<region>.amazonses.com (priority 10) |
| MAIL FROM SPF | TXT | send.example.com | v=spf1 include:amazonses.com ~all |
| DMARC (recommended) | TXT | _dmarc.example.com | v=DMARC1; p=none; |
Copy the exact values from the dashboard or the records array: the DKIM tokens and region are
specific to your domain.
Verification
COSS checks the records automatically; the dashboard and each record's status show the result of
the last check, and can_send says whether live keys may send from the domain. Verification
usually takes minutes, but DNS changes can take longer to propagate. If a domain is not verified
within 72 hours, verification fails. Restarting it (Verify in the dashboard, or
coss.domains.verify(id)) issues new DKIM records to publish.
When several organizations verify overlapping domains, the most specific one decides who may send:
verifying mail.example.com lets you send from @mail.example.com even if someone else verified
example.com.
Tracking domain
A verified domain can serve open and click tracking links from its own subdomain, such as
links.acme.com. See custom tracking domains.