Emergency 10 min read

What To Do in the First 24 Hours After Your Cold Email Inboxes Get Burned

The first 24 hours after a deliverability crisis determine how fast you recover. Here's the exact triage order — what to stop, what to check, and what to do next.

Your campaigns just died. Open rates are at the floor, you're getting spam reports, or your placement test just showed spam across the board. Here's what to do — in order — in the next 24 hours.

Hour 0–1: Stop the bleeding

The most important thing you can do in the first hour is pause sending from affected infrastructure. Every email you send from a burning domain makes the reputation worse. Continuing to send while you diagnose is like patching a leak with water still flowing.

  • Pause all active sequences on the affected inboxes
  • Do not start new campaigns on the same domains
  • Do not attempt to "test" by sending more emails to see if it improves

Hour 1–2: Run the diagnostic stack

With sending paused, run every diagnostic check in parallel. This tells you whether you're dealing with a technical break or actual reputation damage — and the fix is very different.

Authentication check

Check SPF, DKIM, and DMARC on every affected domain. Do this first — a broken auth record will cause spam placement regardless of reputation. Use the SPF checker, DKIM checker, and DMARC lookup.

Blacklist check

Run your domain and sending IPs through the blacklist checker. Note which lists you're on and what severity they are. Spamhaus is critical — others are less urgent.

Placement test

Run a placement test using a clean test email to get the raw server verdict. The authentication results in the headers will tell you exactly what the receiving server saw.

Tracking domain check

Check your tracking domain. A broken or Cloudflare-proxied tracking domain is a common cause of sudden placement drops that looks like a burned inbox.

Hour 2–4: Triage and classify

Once you have diagnostic results, classify each affected inbox into one of three buckets:

  • Technical issue only — auth broken, tracking misconfigured, no blacklisting. Fix the technical issue and retest before deciding anything else.
  • Reputation damage, recoverable — minor blacklisting, short sending history, no spam complaints. Pause, fix auth, request delisting, reduce volume for 2 weeks.
  • Reputation damage, replace — Spamhaus listing, long history of aggressive sending, spam complaints. Begin replacement process immediately.

Hour 4–8: Fix what's fixable

For technical issues, fix them now. DNS changes propagate in minutes to hours. Once auth is fixed, rerun the placement test. Many "burned inboxes" come back to life the moment DKIM is repaired.

For blacklisted domains: submit delisting requests to each blacklist you're on. Spamhaus, Barracuda, and most others have self-service delisting forms. Note: they won't delist you if the underlying problem isn't fixed first.

Hour 8–24: Decide on replacement

If you're managing client campaigns that can't pause for 3–6 weeks while reputation recovers, you need replacement infrastructure running within 24 hours. This is where the math matters — setting up and warming new inboxes from scratch takes weeks. Pre-warmed inboxes can be deployed the same day.

24-hour recovery checklist

  • Pause all sending from affected inboxes
  • Check SPF, DKIM, DMARC on all affected domains
  • Run blacklist check on domains and IPs
  • Run inbox placement test
  • Check tracking domain configuration
  • Check redirect on sending domain
  • Classify each inbox: technical / recoverable / replace
  • Fix any broken auth records
  • Submit blacklist delisting requests
  • Decide on replacement infrastructure if needed
  • Set up monitoring so this doesn't happen silently again

What not to do

Don't keep sending. Don't try "low volume" sends to see if it helps. Don't immediately delete and recreate inboxes without diagnosing first. And don't assume it's the copy — content is rarely the primary cause of sudden spam placement.

If the issue is reputation damage and campaigns can't pause, replacement infrastructure is often the fastest path back. WarmInboxes provides pre-warmed inboxes that can be deployed same-day while your damaged domains recover. But run the checks above first — you may find it's a technical issue that resolves in hours.

Run the checks first

Before replacing anything, run a free inbox placement test. You might find the issue is DNS, not the domain — and save yourself a week of unnecessary work.

Free inbox placement test Check burn score

More guides

How to Tell if Your Inboxes Are Burned or if Something Else BrokeBurned Domain vs Burned Inbox: How to Tell the DifferenceCold Email Deliverability Collapsed: The Step-by-Step Triage Checklist