Skip to main content

Custom Domains

Use your own domain for branded agent email. Anima generates the required DNS records, shows what still needs to propagate, and lets you verify once your provider publishes the changes.

Why use a custom domain?

Send from your own brand, improve trust with recipients, and separate production sending from shared or testing domains.

What you need first

A domain you control plus access to its DNS provider — for example Cloudflare, Route 53, Namecheap, GoDaddy, or another registrar.

How long does it take?

Many DNS changes appear within minutes, but some providers take up to 48 hours to fully propagate.

What Anima sets up for you

Your agents both send and receive mail on a custom domain, so Anima generates a complete set of DNS records covering both directions. You publish them once at your DNS provider; Anima handles delivery, signing, reputation, and inbound routing from there.
DirectionWhat the records do
InboundRoute incoming mail and replies to your agents’ inboxes.
OutboundAuthenticate outgoing mail (SPF, DKIM, DMARC) so recipient mailbox providers trust it.
Your only job is DNS. Once the records verify, sending and receiving work with no further configuration.

1. Create the domain in Anima

Go to Dashboard → Domains, click Add domain, and enter the root domain you want to send from — for example example.com. Once created, Anima opens the DNS setup surface immediately so you can copy the required records without hunting through the table.

2. Copy the required DNS records

Anima generates the ownership TXT, the mail-routing MX records, the DKIM CNAME records, the SPF TXT record, and the DMARC TXT record for you. The product shows both the full record name and the shorter host value most DNS providers expect.
RecordHost exampleWhy it matters
TXT@Verifies that you control the domain.
MXmailRoutes bounce and return-path traffic for outbound mail.
TXTmailPublishes SPF for the dedicated return-path subdomain.
CNAMEtoken-a._domainkeyPublishes DKIM keys so mailbox providers trust mail signed for your domain.
MX@Routes inbound agent mail and replies for the domain.
TXT@ or mergeAuthorizes Anima to send on your behalf via SPF. Merge into an existing SPF record if you already have one.
TXT_dmarcTells inbox providers how to handle failed authentication and where to send aggregate reports.

3. Use the right host format in your DNS provider

This is the most common source of mistakes. Many DNS providers automatically append your root domain, so the safe default is to paste the Host column values from Anima instead of manually reconstructing the full record name.
Avoid entering _dmarc.example.com into a provider that automatically appends example.com — that creates _dmarc.example.com.example.com.

Provider-specific notes

Cloudflare — Usually appends the root domain automatically. Paste the Host column, not the full name. Route 53 — Supports manual entry and zone imports, but review long TXT values carefully if you paste them manually. Namecheap — Uses Host and Value fields. Prefer @, mail, and _dmarc instead of full FQDNs where possible. GoDaddy — Treat the UI as relative hostnames unless the screen explicitly asks for the full record name.
The mail host is reserved for outbound return-path and bounce handling. Leave your apex MX pointed at the inbound record Anima provides so agent mail and replies are delivered.

4. Download the zone file if your provider supports imports

The DNS setup surface includes a Download zone file action. Use it when your DNS provider accepts BIND-style imports — it’s the fastest way to publish all records at once. If your provider does not support imports, copy each record individually from the setup table.

5. Verify and troubleshoot

When you click Verify records, Anima checks each required DNS record and marks it as Valid, Missing, or Invalid. Fix only the rows that fail — if a record already matches, leave it alone and allow DNS time to propagate.

Verification statuses

Missing — The provider has not published the record yet, or propagation is still in progress. Invalid — A record exists, but the value or host is wrong. Compare the row in Anima against what your provider shows. Valid — That record is correct and does not need changes.

SPF merge rule

A domain should publish only one SPF TXT record at the root. If you already use SPF elsewhere, keep the existing record and merge Anima’s include: mechanism into it rather than creating a second SPF TXT record.

Ready to configure your domain?

Open the Domains page to create a domain, copy records, and verify the setup in one place.