Burned Domains: When a New Batch Does Not Help

People hear the domains are burned and reach for a new batch. Sometimes that is correct. Often it is how the next invoice disappears into the same failure. A new domain only helps when something about the send pattern changes: list quality, density, authentication, platform, caps, or offer. If those stay identical, you are buying fresh names for the same behaviour filters already rejected.

This guide is the decision frame. For how domains burn, see Why Cold Email Domains Burn and How to Slow It. For inbox level burns, see Why Cold Email Inboxes Get Burned.

Receiving systems distrust the domain enough that placement collapses. Seed tests land in spam. Replies fall on that domain while other domains may still work. There is no single public switch labelled burned. You infer it from replies, seeds, provider health, and Postmaster when configured.

1. Blacklists and auth. Run every sending domain through a public blocklist lookup tool. Confirm MX, SPF, DKIM, and DMARC still pass. Fix the cause of any listing and any DNS failure before you shop. See Authentication for Cold Email on Google Workspace.
2. Scope. One domain, every domain in the campaign, or every provider?
3. List. Bounce rate and engagement on the segments that ran during the drop.
4. Density and caps. Mailboxes per domain and cold sends per mailbox versus the prior steady state.
5. Platform. Official Google Workspace you admin, or shared SMTP / unknown licence seats?
6. Primary domain check. Did someone put the brand apex into the pool?

If auth is broken or the list is toxic, new domains inherit the same fate. Google's sender guidelines, including the spam rate below 0.3%, do not reset because the registrar receipt is new.

Same list, new domains: Unverified or irrelevant contacts will burn inventory regardless of age. Clean or replace the list first.

Same density, new domains: Five plus mailboxes hammering each domain, or one mailbox sending like a blast machine, recreates the pattern. Keep two or three mailboxes per domain and roughly 20 to 40 cold sends per warmed mailbox per day including follow ups.

Same copy and offer, already rejected audience: If the market muted you, domains are not the bottleneck. Fix targeting and relevance.

Same shared pool underneath: Replacing domains while staying on shared SMTP can mean new names on the same neighbourhood reputation. Change platform if the audit points there. See Dedicated Google Workspace vs Shared Cold Email Infra.

Auth still unfinished: Buying domains without finishing DKIM start authentication is shopping, not infrastructure.

Panic volume on day one: New domains need ramp. Dropping full campaign caps onto fresh seats skips the only advantage a new batch had. See Warmup Myths That Waste Cold Email Teams.

The old domains stay degraded after a rest period at sharply lower volume, and you have already fixed list, caps, and auth plans.

You need more capacity and healthy domains are truly at sane caps.

You are leaving shared SMTP for official Google Workspace on domains you control.

You are separating agency clients into isolated pools (plan dependent multi org).

You are retiring domains tied to a compromised seat after credentials and lists are cleaned. See Mailbox Suspension in Cold Email: Causes and Next Steps.

Even then, buy for a changed plan, not for emotional relief.

1. Freeze volume growth on burned domains; pause the worst segments.
2. Document what changed in the two weeks before the drop.
3. Repair auth and list issues on paper before the registrar checkout.
4. Stand up a small pilot batch (a few domains, two or three mailboxes each).
5. Warm, then ramp; connect in Instantly or Smartlead using documented methods.
6. Compare replies against a held segment. Only then expand.

Keep cold email off the primary domain.

Authenticate before warmup.

Respect density and per mailbox caps.

Rotate across domains. See Mailbox Rotation for Cold Email Infrastructure.

Prefer official Google Workspace seats you admin.

Watch replies and complaints harder than opens.

Do not scale list quality downward to feed a volume target. See Deliverability Dropped After You Scaled: What Changed.

You cannot make domains immortal. You can stop paying tuition for the same mistake.

Executives hear burned and approve spend because domains feel tangible. Bring a one pager:

What broke (list, density, auth, platform), with dates.

What a new batch will change if approved.

What a new batch will not change if those roots stay.

Size of a pilot batch versus a full replacement.

Success criteria in human replies after two weeks, not opens on day one.

You are not blocking growth. You are stopping a second burn invoice.

For each candidate old domain: age in pool, mailboxes counted, peak daily cold sends, bounce rate, reply trend, auth status, platform type, blacklist notes. For the proposed new batch: domains count, mailboxes per domain, target caps, list segment, warmup plan, sequencer connection method. If the two columns look identical except for domain names, do not check out.

Expand in steps. Keep older domains only if they still earn replies; rest a slipping domain before you retire it, and retire gradually. Do not mix burned and healthy domains in one rotation pool to use inventory. Rotation across weak seats slows the recovery of strong ones. See Mailbox Rotation for Cold Email Infrastructure.

ColdMail provisions official Google Workspace on dedicated domains with automated SPF, DKIM, DMARC, and MX, admin access with 2FA, and provider health indicators for Gmail, Outlook, and Yahoo to help you spot which domains need attention. AI warmup is available as an optional add on; see coldmail.app for current add on pricing. Mailboxes are ready to connect in Instantly and Smartlead using the methods those tools support. ColdMail does not promise domains never burn; it reduces common setup causes and keeps control in your admin panel.

If you are about to buy a panic batch, Book a Strategy Call first, or set up a cleaner pilot at coldmail.app.