July 9, 2026 · 3 min read
Choosing a sending domain for your app
Your customers should receive email from a domain they recognize. That can be your root domain, such as yourapp.com, or a dedicated sending subdomain, such as send.yourapp.com.
Both are valid. The right choice is the one that matches how you run DNS and how you want customer-facing mail to look.
Start with the address your customer expects
If your product already sends from [email protected] and customers recognize it, use yourapp.com. You do not need to create a subdomain just because an email provider recommends one.
If you are starting a new product, managing several applications, or want to keep mail records separate from your website records, send.yourapp.com is a tidy default. It gives your sending configuration its own place without changing the address customers see.
Verify the DNS records before sending production mail
NoticeAPI generates the ownership, SPF, and DKIM records for the domain you add. Install them with the Cloudflare flow or copy them into your DNS provider, then verify the domain from the dashboard.
DNS changes are often visible within minutes, but propagation depends on your provider and existing DNS configuration. Keep the records in place after verification: they are how receiving providers confirm that NoticeAPI is authorized to send for your domain.
Keep transactional and marketing mail intentional
The same verified domain can send transactional mail such as receipts and password resets, plus consent-based product updates through Broadcasts. NoticeAPI still applies suppressions, recipient controls, and unsubscribe behavior where the message type requires it.
If you operate several products or client domains, keep each sender in its own project. That keeps domains, API keys, logs, webhooks, and operational controls in the right context.
Add your domain when you are ready
Create or connect a scoped API key, add the domain you want to send from, verify its DNS records, then wire your first customer-facing email.