Replace a burned domain in zero clicks.
Spaceship → Cloudflare → Workspace → Instantly → warmup. The ten-hour playbook, run end-to-end by Mailnurse while you sleep.
The ten-hour playbook nobody actually runs.
Replacing a burned sending domain takes roughly two hours of Spaceship registration, an hour of Cloudflare DNS, three hours of Workspace tenant setup, two hours of Instantly mailbox provisioning, and two hours of warmup configuration. Each step is fragile. Each step is manual. Each step is the reason agencies tolerate burnout instead of fixing it.
-
Domain registration → DNS configuration → Workspace tenant → Instantly mailboxes → warmup setup is a five-system, thirty-plus-click marathon.
-
Half the burned-domain replacements get deferred indefinitely because the operator doesn't have time today.
-
Manual rotation introduces typos: misspelled DNS records, wrong SPF includes, forgotten DMARC policies. The replacement domain burns within days.
kelthorn.com → drovexal.com
Step 3 of 5 · ~6m remaining- 01 doneSpaceshipDomain purchased
- 02 doneCloudflareDNS zone live
- 03 runningWorkspaceTenant provisioning…
- 04 queuedInstantlyMailboxes pending
- 05 queuedWarmupSchedule queued
End-to-end provisioning, no human in the loop.
- 01
Detect.
When monitoring trips a replace threshold (or you fire one manually), Mailnurse marks the burned domain for retirement and selects a replacement candidate from your pre-staged pool.
- 02
Provision.
Spaceship buys the domain. Cloudflare receives the DNS zone. Workspace creates the tenant. Instantly receives the mailboxes. Warmup begins on a graduated schedule. Every step is logged.
- 03
Hand off.
When the new domain passes its first vitals threshold, it joins your active fleet. The retired domain is paused, archived, and its automation log is preserved for audit.
Five systems, one continuous tape.
Pre-staged domain pool.
Mailnurse keeps a buffer of clean, age-warmed domains ready to deploy. Rotation isn't reactive — the replacement is already half-warmed when burnout is detected.
Automation log.
Every provisioning step is recorded with timestamp, payload, and outcome. When something fails — and at this scale, something occasionally fails — the audit trail tells you exactly where.
DNS verification.
SPF, DKIM, DMARC, MX, and reverse-DNS are all verified post-deploy before the domain is handed to warmup. Typos cannot propagate.
Graduated warmup.
New domains start at three sends per day and climb across two weeks. The schedule is locked to the deliverability literature, not arbitrary intuition.
How rotation works, and what stays in your control.
Do I need accounts at Spaceship, Cloudflare, Workspace, and Instantly?
What if a step fails mid-provision?
Can I trigger a rotation manually?
How does the pre-staged pool work?
Two disciplines that compound this one.
Health monitoring
Continuous placement testing, 11-DNSBL probes, warmup vitals every four hours. A composite risk score per account so decay is visible before deliverability collapses.
Read more 03Auto-pause spam
When bounce velocity climbs, DNSBLs hit, or placement drops, the rules engine pauses sends before the campaign goes wider. Eight codified rules with severity tiers.
Read moreCare, expressed as precision.
Cold-email infrastructure that watches itself — so you can focus on the campaign, not the chassis.
14-day free trial · No credit card · Instant setup