Domains
Add & verify a domain
Add your sending domain, publish the DNS records Deckle generates, and let verification poll until you're ready to send.
Every email you send through Deckle goes out from a domain you own. Adding one takes a few minutes: point a handful of DNS records at your provider, and Deckle watches for them to propagate.
Why your own domain#
Deckle follows Model A — you send from your own verified domain rather than a shared “from” address owned by the platform. That means the sending reputation you build is yours alone.
On a shared pool, one careless sender’s spam complaints can drag down deliverability for everyone on the same IPs. With your own domain, that can’t happen: a bad sender elsewhere never poisons your inbox placement, and the trust you earn with mailbox providers stays attached to your domain.
- Recipients see mail from your domain, not a generic relay address.
- Your engagement, bounce, and complaint history define your reputation.
- Authentication (DKIM, SPF, DMARC) is signed under your domain.
Add a domain#
Domains live in the account menu — open Domains from the top bar. Adding a domain creates the underlying AWS SES identity and hands you the DNS records to publish.
Open Domains and add your domain
acme.com.Deckle creates the SES identity
Add the records at your DNS provider
Let verification auto-poll
pending, verified, or failed. DNS changes can take anywhere from a few minutes to a few hours to propagate. Use the one-click Recheck button to poll again on demand.What the records look like#
Each domain publishes three kinds of records. The exact tokens are unique to your domain — copy the real values from the domain’s page.
| Record | Type | Host | Purpose |
|---|---|---|---|
| DKIM (×3) | CNAME | <token>._domainkey.acme.com | Signs your mail so mailbox providers can verify it wasn’t altered. |
| SPF | TXT | @ | Authorizes SES to send for you — v=spf1 include:amazonses.com ~all. |
| DMARC | TXT | _dmarc.acme.com | Sets your alignment policy — start with v=DMARC1; p=none. |
DKIM is what gates sending; SPF and DMARC are verified by real DNS lookups and reported per record. See Authentication for the full breakdown of each record.
DKIM must verify before you can send
Deckle only unlocks sending from a domain once its DKIM records are attested by SES. Until the domain showsverified, sends from that address are blocked. SPF and DMARC are strongly recommended (and required by Gmail and Yahoo bulk-sender rules) but don’t gate a single transactional send on their own.Default sender#
Each verified domain carries a default from name and address. Set these on the domain’s page — for example a name of Acme and an address of hello@acme.com.
The default sender fills in the from field when you compose a campaign or start an automation from that domain, so you don’t retype it every time. You can always override it per send — the from value on an API call just needs to belong to a verified domain, in the form "Name <addr@domain>" or a bare addr@domain.