Launch a new sending domain
Take a new domain from DNS and authentication through first production sends.
- Difficulty:
- Intermediate
- Prerequisites:
- DNS access, ESP/MTA account, Engaged seed list
- Last updated:
- 2026-07-15
- Author:
- empire
Objective
Prepare a domain for sending
Ready DNS and identity signals before production volume.
Starting state
Domain registered; ESP or MTA selected
Prerequisites
- DNS access
- ESP/MTA account
- Engaged seed list
Estimated time
1–2 hours
Difficulty
intermediate
Required access
- DNS
- ESP admin
- analytics
Inputs
- Domain
- Sending stream type
- Initial volume plan
Step-by-step instructions
- Prepare DNS and identityPublish MX/tracking hosts as needed and choose From subdomain strategy.
- AuthenticateConfigure SPF, DKIM, and DMARC before any marketing volume.
- Warm and launchStart with engaged cohorts, then expand only after metrics hold.
Verification
- Auth passes on samples
- First-week complaint/bounce within policy
Common mistakes
- Launching peak volume on day one
- Separate transactional vs marketing subdomains at launch?
Rollback / recovery
- Pause campaigns and hold at seed volume until auth/reputation stabilize
Expected outcome
Domain is live with authenticated mail and a controlled ramp.
When to escalate
- Hard blocks during first production week
Related Learn Articles
- DNSDomain Name System — the lookup fabric email authentication depends on.
- SPFSender Policy Framework — authorizes hosts that may send for a domain.
- DKIMDomainKeys Identified Mail — cryptographic signatures for message integrity.
- DMARCDomain-based Message Authentication, Reporting, and Conformance.
- WarmupControlled introduction of sending volume so mailbox providers learn to trust a domain or IP.