Domains & DNS

Production email sends from your domain. Add the domain you want to use in the portal, publish the DNS records we generate, and hit verify. A subdomain like send.yourapp.com is often easier to manage, but a root domain works too.

Managing several products or client senders? Read the multiple sending domains guide.

What the records do

Verification

DNS propagation usually takes minutes, occasionally hours. Verification re-checks automatically once started; the domain page shows per-record state. When all required records verify, the domain flips to verified and any address at it can send. Sender identities (the local part before @) are provisioned automatically on first use, including display names.

Plans and domain counts

Free includes one verified sending domain. Pro includes ten domains, then extra domains are billed at $1/domain/month until the custom-plan threshold. Deleting a domain stops its sending immediately and releases the slot. Root domains and subdomains are both supported; a dedicated subdomain can make app, web, and email DNS easier to reason about.

Warm-up

New accounts ramp daily sending limits automatically (day one is small, limits grow each day). This is deliberate: inbox providers distrust brand-new domains that suddenly blast volume, and the ramp is what keeps your long-term deliverability high. Hitting the ramp returns 429 daily_limit_reached.

Open & click tracking

Each verified sending domain has open and click tracking toggles. Tracking is off by default. These toggles become the defaults for sends from that domain, and API calls can override them with tracking.opens or tracking.clicks. When enabled, NoticeAPI adds an open pixel or wraps HTTP links, then records email.opened and email.clicked events in logs, metrics, timelines, and webhooks.