Latest field note3 min read
Choosing a sending domain for your app
Use your root domain or a dedicated subdomain for production email, then verify the DNS records that prove you can send.
Read the field noteEmail guides, without the fog.
Practical guides for transactional email, sending domains, delivery events, and the operational work that starts after the API call.
Inside this guide
- Choose the senderRoot domain or dedicated subdomain
- Install the proofOwnership, SPF, and DKIM
- Keep the context cleanOne project for each product or client
Start where the work gets specific.
Each field note begins with a real decision in an email workflow and ends with something you can verify.
Which domain should customers see?
Choose the root domain or a dedicated sending subdomain, then publish the records that prove authorization.
Open domain setupWhich call belongs in the app?
Use the REST API, typed Node SDK, or SMTP relay for the customer message your product needs to send.
Open send docsWhat happened after the API call?
Read the stored email, recipient timeline, suppression state, and signed delivery event from one record.
Open email retrievalPublished guides.
A short, useful archive for the parts of email you still have to operate after integration.
1 published guideOpen the docs beside your code.
Use the field notes for decisions. Use the documentation for endpoints, fields, and setup.