Instant domain swap: replace a burned cold email domain without losing a send
When a cold email domain burns, the fix usually costs days of lost sends and manual inbox shuffling. Here's the manual process, and how an instant domain swap removes it.
- Burned domains are a normal cost of sending cold email at volume. The expensive part isn't the domain. It's the send time you lose while replacing it.
- Done by hand, a replacement means pausing campaigns, pulling inboxes out of the sequencer, connecting new ones, re-attaching them to every campaign and resetting caps. Then you wait for warm-up.
- Warm-up is what makes it slow: 10–14 days for Outlook tenants, 15–25 days for Google Workspace, 4–6 weeks for private SMTP.
- The fix is a warm reserve. Keep 50% extra capacity warm, and swap a reserve domain into every affected campaign the moment one burns.
- Zylar does that swap automatically, so the campaign keeps sending on schedule.
Every team sending cold email at volume burns domains. A list goes bad, a copy angle draws complaints, a provider tightens its filters. You can't send hundreds of thousands of emails a month and never lose a domain. What you can control is how much each loss costs you.
Most of that cost isn't the domain itself. It's the days your campaigns sit under-capacity while someone does the replacement by hand, and the weeks a new domain needs before it can send.
What does replacing a burned domain cost you today?
Here's the manual process in most sequencers, once you've spotted that a domain is in trouble:
- Pause every campaign the domain's inboxes send for, or watch it keep sending into spam.
- Remove the domain's inboxes from the sequencer, or at least from every campaign.
- Buy a replacement domain and set up the redirect.
- Publish SPF, DKIM and DMARC, and a tracking domain, and wait for DNS.
- Create the inboxes. That's 5 per domain on Google or SMTP, and up to 100 on an Outlook tenant.
- Connect them to the sequencer and start warm-up.
- Wait for warm-up to finish.
- Attach the new inboxes to every campaign the old ones were in, and set their daily caps.
- Resume the campaigns, and check that nothing was double-sent or skipped.
Steps 1, 2, 8 and 9 have to be repeated for every campaign, in every workspace, for every client that used the burned domain. At agency scale, one bad domain can touch a dozen campaigns.
Step 7 is where the time goes:
| Inbox type | Minimum warm-up | Recommended before cold sends |
|---|---|---|
| Outlook Premium | 3–5 days | 10–14 days |
| Outlook Normal | 5–7 days | 10–14 days |
| Google Workspace | 15 days | 20–25 days |
| Private SMTP | 3–4 weeks | 4–6 weeks |
Warm-up figures are from our 2026 Q3 inbox-types data. If you start warming the replacement only after the old domain burns, those campaigns run short for one to six weeks.
Why can't you just send harder from the remaining domains?
It's the obvious workaround, and it's how a single burned domain turns into three. Every inbox type has a safe daily rate: 15–20 cold sends on Google, 8–10 on Outlook Premium, 3–5 on Outlook Normal and 11–14 on SMTP. Push the healthy inboxes past it to cover the gap, and you put their reputation at risk at the exact moment you can least afford it.
The volume has to go somewhere that's already warm.
The fix: a warm reserve and an instant swap
Two things together remove almost all of the cost.
1. Keep a warm reserve. Hold 50% of your sending capacity as domains that are bought, authenticated, connected and on warm-up, but not yet sending cold. They cost money every month, but they turn a replacement from a multi-week project into a same-day switch. How many inboxes you need has the sizing, and what cold email really costs has the price of carrying that reserve.
2. Swap in place, not by hand. When a domain burns, a reserve domain should take over the old one's place in every campaign it was attached to: same campaigns, same schedule, same caps for its inbox type. Nobody has to remove inboxes from the sequencer, add new ones and re-attach them campaign by campaign.
| Manual replacement | Instant swap from a warm reserve | |
|---|---|---|
| Send time lost | Days to weeks, until warm-up finishes | None, the reserve is already warm |
| Campaigns to edit | Every campaign that used the domain | None |
| Risk of over-sending the healthy inboxes | High, it's the usual workaround | None, volume moves to warm capacity |
| Work per burned domain | Hours of manual work across workspaces | Replace the burned domain in the reserve later |
How Zylar's instant domain swap works
This is the operational problem Zylar is built around. When a domain burns, or its placement drops below your threshold and it auto-pauses, Zylar swaps a warm domain from your reserve into every campaign the burned domain was attached to. Sending continues on schedule. The burned domain goes back on warm-up, so it can recover or be retired.
It sits on top of what Zylar already monitors:
- Placement tests per domain on Gmail and Outlook, plus a daily health score for every inbox. That's how a slipping domain gets caught before it lands everything in spam.
- Per-type sending caps, rotation and time-zone windows, so the swap moves volume onto inboxes running within their safe rate.
- One dashboard across every workspace, showing which domains, inbox types and IPs perform and which are burned. That way you can see whether it's one domain or a pattern.
Your remaining job is restocking the reserve: buying and warming domains to replace the ones you retire. Inboxes are available through MailDeck as an add-on, and Zylar checks every new domain's DNS the moment you connect it.
What should you do with the burned domain?
Don't delete it straight away. Take it out of cold sending, keep it on warm-up, and watch its placement. Some domains recover after a few weeks of clean warm-up traffic; others never do. The triage steps, the recovery ramp and when to retire a domain for good are in how to recover a burned cold email domain.
Then fix the cause, or the replacement will burn the same way. The usual suspects: list quality, a volume spike, copy that draws complaints, or, on Outlook, links, tracking pixels and long copy. The infrastructure checklist covers prevention.
FAQ
What is a domain swap in cold email?
A domain swap replaces a burned or paused sending domain with a healthy one in every campaign that used it. Done instantly from a warm reserve, campaigns keep sending on schedule with no manual editing of inboxes or campaigns.
How long does it take to replace a burned cold email domain?
By hand, the setup takes hours and the warm-up takes 10–14 days for Outlook tenants, 15–25 days for Google Workspace and 4–6 weeks for private SMTP. With a warm reserve and an instant swap, the replacement is immediate.
How big should my warm reserve be?
Keep about 50% of your sending capacity warm as a reserve. At 100,000 sends a month on a 50/30/20 Outlook, SMTP and Google stack, that's roughly 39 sending domains plus about 20 in reserve.
Can I just raise sending limits on my other domains instead?
You shouldn't. Each inbox type has a safe daily rate, and pushing healthy inboxes past it to cover a burned domain is how one burned domain becomes several. Move the volume to warm reserve capacity instead.
Does Zylar delete the burned domain?
No. The burned domain is taken out of cold sending and put back on warm-up, so it can recover. Retire it only if placement doesn't come back.
