Warm-up10 min read

Domain warmup failed: signs, causes, and how to restart

Four weeks of warmup, a confident green dashboard from your tool, and then the first real campaign hits 30% inbox at Gmail. Here is how to read the symptoms, identify the actual cause, and decide whether to recover the domain or start fresh.

A failed warmup is rarely a single dramatic event. It's usually a quiet drift — placement gradually weakening over the last week, Postmaster reputation never moving from Low, a complaint or two getting through, a 4xx deferral cluster from Outlook nobody noticed. By the time the real campaign goes out and lands in spam, the warmup hasn't failed in the last 24 hours; it failed two weeks ago and nobody caught the signals.

TL;DR

Symptoms of failure: Postmaster stuck at Low/Bad, sub-60% inbox in seed tests, blacklist hits, rising bounce or complaint rate. Root causes are usually volume bursts, bad lists, missing DKIM/DMARC alignment, or insufficient engagement. Recovery is possible if the cause is fixable; if Spamhaus listed you or Postmaster shows Bad for 7+ days, start fresh on a parallel domain.

Symptoms that warmup didn't take

Five concrete signals that the warmup is in trouble. Any single one is a yellow flag; two or more is red:

  • Postmaster reputation flat at Low or Bad past day 21. A healthy warmup moves from no data → Low → Medium between days 14 and 28. Stuck at Low means the engagement model isn't building.
  • Seed test inbox under 60% at Gmail or Outlook. A properly-warmed domain hits 80%+ at both. Anything sub-60% is failure.
  • Any blacklist hit. Spamhaus, Barracuda, SORBS, URIBL. Even a transient listing is a signal that filters are treating you as adversarial.
  • Bounce rate trending up. Bounces over 2% in any week of warmup mean list-quality damage compounding. Past 5%, the warmup is dead.
  • Complaint rate above 0.3%. Postmaster will show this directly. At 0.3% you're flagged as spam-likely; at 0.5% you're effectively delivering to spam folders by default.

Root cause #1: volume bursts

The most common single cause. Warmup tools and ESPs both let you configure ramp curves, but humans skip days, run catch-up batches on Mondays, or test campaigns mid-warmup. Any sudden jump from 50/day to 500/day on a fresh domain reads to filters as a compromised account starting to send spam.

Symptom signature: placement was fine through week 2, then dropped sharply after a specific day. Check your send logs for a volume spike on or near that day.

Fix: pull volume back to one day before the spike. Hold for 5 days. Resume the curve from there at the original cadence. Do not try to compound recovery with another spike.

Root cause #2: bad list quality

Sending to invalid, role, or recycled spam-trap addresses during warmup is uniquely damaging because the domain has no reputation cushion. A 5% bounce rate on a warmed domain is bad; the same 5% on a warming domain is catastrophic, because every bounce is weighted as evidence the sender is using a low- quality list.

Symptom signature: bounce rate above 2% at any point, soft bounces clustering around specific provider domains (Gmail soft-bouncing 4xx is a common late-warmup signal), or appearance on a spam trap blacklist.

Fix: stop sending immediately. Validate the entire list with a verification service (NeverBounce, ZeroBounce, MillionVerifier). Discard anything risky. Resume warmup with the validated list only — and only after 3 days of pause to let signals settle.

Root cause #3: authentication misalignment

SPF passes but DKIM signs with a different domain than the From header. DMARC therefore fails alignment. Filters treat DMARC failure as evidence of spoofing — even when the message is legitimately yours. A misaligned warmup builds reputation for the wrong domain (the DKIM signing domain) instead of the intended sending domain.

Symptom signature: Postmaster shows authentication pass rates below 95%. Specific provider patterns of placement to spam (Yahoo and Apple are particularly strict on alignment).

Fix: configure DKIM with a selector for the same organisational domain as the From header. Republish SPF to authorise the actual sending IP. Set DMARC to p=none initially while you verify alignment, then move to p=quarantine. Continue warmup from current volume.

Misaligned DKIM is silent

The most insidious failure: a domain warming for 4 weeks with DKIM signing as "mailgun.org" instead of your domain. Engagement signals build reputation for Mailgun, not you. Check your DKIM signing domain matches your sender domain before day 1.

Root cause #4: insufficient engagement

The biggest failure mode for tool-only warmups. The volume curve looks perfect, the daily counts hit their targets, but the engagement signals don't move because warmup pool replies and folder moves are increasingly discounted by Gmail and Outlook. The domain has "sent volume" but no evidence anyone wanted to receive it.

Symptom signature: Postmaster reputation stays Low through week 4. Seed test inbox is mediocre but not catastrophic (50–70%). No specific failure event — just chronic underperformance.

Fix: introduce real human engagement during the recovery period. Send genuine business updates to a real list of engaged contacts (advisors, customers, opt-ins) that ask for and reliably get replies. Aim for 10%+ reply rate over 7 days of recovery sending. Gmail's reputation responds within two weeks to genuine engagement at this scale.

Root cause #5: content patterns

A warmup conducted with bland content masks issues that emerge when real campaign content goes out. Spam-trigger phrases, heavy HTML, multiple links, image-heavy formatting, suspicious attachments — any of these can shift placement from inbox to spam without the domain reputation actually being the problem.

Symptom signature: warmup-period seed tests good (80%+), but the moment real campaign content goes out the inbox rate collapses. Different subject lines produce wildly different placement.

Fix: simplify the campaign content. Plain-text or lightly formatted HTML, one link maximum, no images, conversational subject lines. Once real content is hitting inbox at acceptable rates, you can carefully reintroduce formatting elements one at a time.

When to recover vs restart

Some failures are recoverable; some require a fresh start on a new domain. The decision rule:

  1. Spamhaus DBL listing. Restart. Even after delisting, Gmail's internal memory of the listing persists for months.
  2. Postmaster Bad reputation for 7+ consecutive days. Restart. Bad rating compounds over time and is very hard to claw back.
  3. Complaint rate above 0.5% with no clear single-campaign cause. Restart. Persistent high complaints mean the engagement signal is structurally negative.
  4. Volume burst, single event, identifiable. Recover. Pull back, hold, resume.
  5. Authentication misalignment, recently fixed. Recover. Continue from current volume with corrected auth.
  6. Insufficient engagement, no other failures. Recover. Add real engagement during a 2-week recovery period.

The fresh-domain restart pattern

If recovery isn't viable, restart on a different domain. The pattern:

  • Buy a fresh domain from a reputable registrar — different from the failed one. Don't reuse the same brand suffix (e.g., if yourcompany.com failed, don't go to yourcompany.io next; filters notice the pattern).
  • Set up auth correctly from day one — SPF, DKIM aligned with the sending domain, DMARC starting at p=none.
  • Run the full 4-week warmup curve. Don't accelerate to "catch up" for the failed attempt.
  • Use the failed domain's diagnosis to inform the new warmup — if engagement was the problem, prioritise real human engagement on the new domain from day 1.

Parallel-domain strategy

Serious senders run multiple domains in parallel from the start precisely so a single warmup failure doesn't halt the entire operation. Three to five domains warming concurrently gives you fault tolerance — if one fails, the others continue and you investigate without business pressure on the recovery timeline.

Setup: variations of the brand (yourcompany.com, yourcompany.co, getyourcompany.com), all warming on the same cadence, all with proper auth, all monitored independently. Cost: trivial — domains are $10/year each. Benefit: never having to choose between "launch on a damaged domain" or "wait another month".

Frequently asked questions

How long does a recovery take if it works?

Two to four weeks of corrected sending typically restores Postmaster reputation by one tier (Bad to Low, Low to Medium). Expect to lose any time pressure on the launch — recovery is incompatible with launching the next day.

Can I just send less to a damaged domain and let it heal?

No. Reputation requires active sending with positive engagement to rebuild. Pausing sending lets reputation decay further (Gmail expects continued evidence of legitimate use). Healing requires sending differently, not sending less.

If I restart on a fresh domain, does the failed domain pollute it?

Only if they share infrastructure (same SPF includes, shared IPs at the same ESP, same brand patterns). Use separate ESPs or separate sending IPs for the new domain. The DNS-level relationship is what filters watch.

Should I tell my ESP about the failure?

Yes if you're on a shared IP with that ESP. Your damaged reputation may be affecting other tenants and the ESP may quarantine your account. Better they hear it from you with a recovery plan than discover it from a complaint cluster.
Related reading

Check your deliverability across 20+ providers

Gmail, Outlook, Yahoo, Mail.ru, Yandex, GMX, ProtonMail and more. Real inbox screenshots, SPF/DKIM/DMARC, spam engine verdicts. Free, no signup.

Run Free Test →

Unlimited tests · 20+ seed mailboxes · Live results · No account required