When to Retire a Cold Email Domain (and When to Rest It Instead)

Rest a cold email domain when the damage is recent and you have fixed the cause. Retire it when the bad signals persist for weeks after the fix, or when the inbox provider has closed the accounts. A bounce spike from one dirty list, a short burst of spam complaints or a temporary throttle usually recovers with a pause and a slow restart. A Gmail spam rate that stays at or above 0.3%, a domain blocklist listing that will not clear, or seed tests that land in spam everywhere despite clean authentication are reasons to retire. Either way, find the cause first: a fresh domain fed the same list fails the same way.

Secondary domains are built to be replaceable. Our guide to setting up secondary domains covers why. Swapping them too early wastes warm-up time, and swapping too late burns pipeline.

Signals, and what each one means

Signal	Where you see it	Usually means
Bounce rate jumped on one campaign	Sequencer stats, bounce messages	A list problem. Rest the inboxes, clean the list. Not a retirement signal by itself
Gmail spam rate at or above 0.3%	Google Postmaster Tools	Recipients are marking you as spam. Google's sender guidelines (read 2 Nov 2026) ask senders to stay below 0.3% and recommend under 0.1%
"Very low reputation of the sending domain"	Gmail bounce text	Domain reputation at Gmail is poor. See Gmail low domain reputation
Domain on a domain blocklist	A blacklist check	Listing tied to the domain itself, not your IP. See Spamhaus lists explained
Seed tests in spam at several providers	Inbox placement seed tests	Broad reputation damage, if authentication passes
Replies collapsed on unchanged copy and list type	Sequencer reply stats	Possible silent spam-foldering. Confirm with a seed test before acting
Accounts suspended or restricted	Workspace or Microsoft admin	The provider has acted. See Workspace suspended or Microsoft restricted sender

One signal for a week is a reason to slow down and look. Several signals together, still there two to four weeks after the fix, is a reason to retire.

First, find the cause

A domain gets burned by something you did, and that something comes with you to the next domain. Before deciding anything:

1. Pull the bounce messages and sort them. Paste them into Bounce Doctor to split bad addresses from sender blocks. Lots of "user unknown" means the list. Lots of 5.7.x policy and reputation rejections means the sending.
2. Check authentication on every domain. One broken DKIM record can look like reputation damage. The bulk email authentication checker checks many domains at once.
3. Look at what changed. A new lead source, new copy, a higher daily cap, new tracking links, a new list segment.
4. Read our diagnosis guide. Is it my list or my domain? walks through the split step by step.

If the cause was a bad list, the fix is to verify and suppress, and the domain may only need rest. If the cause was targeting that people do not want, a new domain will collect complaints just as fast.

How to rest a domain

Resting is a short, deliberate pause, not just switching campaigns off and hoping.

Week	What to do
1	Stop all prospect sends from the domain's inboxes. Fix the cause. Keep replies and existing conversations going
2-3	Keep the inboxes lightly active: real replies, internal mail, or your warm-up tool at low volume
3-4	Restart at about a quarter of the old daily cap, sending only to freshly verified valid addresses
After	Ramp back up over two to three weeks if bounces, complaints and placement look normal

These are working rules, not published thresholds. Google and Microsoft do not say how long recovery takes, and anyone quoting an exact number is guessing. Our 30-day sender reputation recovery plan has more detail on each week.

When to retire

Retire the domain when any of these is true:

• Postmaster Tools spam rate stays at or above 0.3% for weeks after you cut volume and fixed targeting.
• A domain blocklist listing will not clear, or keeps coming back. Our guide to getting off a blacklist covers the removal routes first.
• The provider closed or permanently restricted the accounts and appeals failed.
• Restarting at low volume to a clean list still lands in spam at several providers.
• The cost of recovery is more than the cost of a replacement. A new domain plus three inboxes plus three weeks of warm-up is a known cost. Weeks of low-volume nursing with no pipeline may be worse.

How to retire a domain without losing leads

1. Stop new prospect sends from every inbox on the domain.
2. Keep the inboxes open for replies. People reply to old threads weeks later. Keep the mailboxes until replies stop coming in.
3. Move live leads to a warmed replacement. In most sequencers you can reassign the remaining steps to other inboxes. Make sure leads already contacted continue from their next step rather than restarting at step 1.
4. Re-verify those leads before they move. They were verified for the old campaign weeks ago, and some will have gone stale. A re-check of just the moving leads is a small job.
5. Keep the domain registered. Leave MX records in place so replies still arrive. If the domain lapses, someone else can register it and receive mail meant for you. Set it to auto-renew.
6. Leave SPF, DKIM and DMARC published while the inboxes exist, so the occasional reply you send still authenticates.
7. Record what happened: the domain, dates, cause and signals. The next retirement decision goes faster with that history.

Keep a bench of warmed spares

A retirement only hurts the pipeline if the replacement starts cold. Teams that send at scale keep a few domains and inboxes warming at all times, so a burned domain is swapped in days, not weeks.

Active domains	Spares warming (rule of thumb)
1-5	1
6-15	2
16-30	3-4

Spares cost a small monthly amount per inbox. Size the active fleet first with how many domains you need for cold email, then generate names with the free cold email domain generator and check availability with bulk domain availability. Warm them on the warm-up schedule.

Stop the next one before it starts

Most burned domains trace back to a handful of causes: unverified or stale lists, too many emails per inbox, and targeting that draws complaints. The habits that prevent them:

• Verify every list close to launch and send only to valid rows. Treat catch-alls as their own small segment.
• Keep daily caps per inbox low. See cold emails per day per inbox.
• Suppress every hard bounce across all campaigns. See cold email suppression lists.
• Watch weekly: Postmaster spam rate, bounce rate per campaign, and a monthly seed test.
• Act on the first spike. Our post on what to do after a high bounce rate is the first-24-hours plan.

Where SimpleVerifier fits

A clean list will not repair a damaged domain, but it removes the most common cause of one. SimpleVerifier checks each address with a live mailbox check, returns catch-alls as risky with a grade, and returns rows it could not check for retry rather than calling them valid. Use it before every launch and before moving leads to a replacement domain.

The first 100 checks are free with a Google sign-in on the verify page. Starter is $9 a month for 2,500 checks, and Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off. See the pricing page.