ColdOps
All posts
Deliverability

Why are my cold emails going to spam? A 2026 fix checklist

By Mo Charradi, Founder7 min read

Cold emails go to spam for one of four reasons: broken authentication, low sending reputation, content that trips filters, or too much volume too fast. Every "why are my cold emails going to spam" rabbit hole ends at one of those four — and you can diagnose all of them in about fifteen minutes. This checklist walks them in the order mailbox providers actually weigh them.

Before you change anything, ask what changed in the last two weeks. Deliverability rarely collapses on its own — a new domain went live, a record got edited, volume jumped, or a list went stale. Find the change and you've usually found the cause.

1. Authentication: SPF, DKIM, and DMARC

This is the first gate, and as of 2024 Google and Yahoo require all three for bulk senders. If any are missing or misaligned, a growing share of your mail is filtered or rejected outright before content is even scored.

  • SPF authorizes the servers allowed to send for your domain.
  • DKIM cryptographically signs each message so the recipient can verify it wasn't altered.
  • DMARC tells receivers what to do when SPF or DKIM fail, and where to send reports.

The common failure isn't a missing record — it's a misaligned one. Your DKIM signs for mail.yourdomain.com but your From address is you@yourdomain.com, and DMARC alignment fails silently. You'll still send; you'll just quietly land in spam.

Check all three in one shot: run your sending domain through the free deliverability checker — it flags missing or misaligned SPF, DKIM, and DMARC plus blacklist status and domain age.

If authentication is broken, stop here and fix it first. Nothing below matters until this passes.

2. Sender reputation: the score you can't see

Once auth passes, mailbox providers judge you on reputation — a rolling score built from how recipients treat your mail. It's the single biggest lever after authentication, and the hardest to fake.

What moves it:

SignalDirectionWhat providers want
Spam complaintsDown, fast< 0.3% (ideally < 0.1%)
BouncesDown< 2%
Spam-trap hitsDown, hardZero
Replies & opensUpReal engagement
Consistent volumeUpNo spikes

A cold domain has no reputation at all, which is why brand-new domains land in spam even with perfect auth — the provider has no history to trust. That's what warmup solves: weeks of low-volume, high-engagement sending that builds a track record. Skipping warmup is the most common self-inflicted cause of cold emails going to spam.

Spam-trap hits are the reputation killer to fear most. Traps are addresses that only exist to catch senders scraping or buying lists. Hit one and you can land on a blacklist that tanks the whole domain. The fix is upstream: verify every list, never buy contacts, and remove anything you can't source.

3. Content: what still trips filters in 2026

Filters have moved past simple keyword matching, but structure and intent signals still matter — especially for a cold email, where the recipient has no prior relationship with you.

The patterns that hurt:

  • Spammy phrasing — "act now," "100% free," "guaranteed," "risk-free." Not because of the exact words, but because they cluster in mail people report.
  • Link-heavy, image-heavy messages. One link is fine. Five links, a tracking pixel, and an image banner reads like a newsletter, not a personal email.
  • Bad text-to-HTML ratio. Plain, personal-looking mail outperforms designed templates for cold outreach. Send like a human typing to one person.
  • Open-tracking pixels. In 2026, tracking pixels are an increasingly strong spam signal — and Apple Mail Privacy Protection has made open data mostly noise anyway. Turn open tracking off.
  • Link tracking on a shared/burned domain. If your click-tracking domain has a bad reputation, it drags your mail down with it.

Not sure which words are hurting you? Paste your copy into the free spam word checker — it scores trigger words and structural red flags before you hit send. For a full breakdown of which words and phrases reliably land mail in spam — and the safer alternatives — see the cold email spam trigger words guide.

4. Volume and velocity: sending too much, too fast

Even with clean auth, good reputation, and tight copy, you can spam-flag yourself with volume. Mailbox providers watch rate of change as closely as absolute numbers.

  • Cap per mailbox. In 2026, keep it to roughly 20–40 sends per mailbox per day on a warmed domain — not the hundreds some tools will happily let you configure.
  • Ramp, don't jump. Going from 10 to 200 sends overnight looks like a compromised account. Scale volume by adding mailboxes and domains, not by cranking one inbox.
  • Spread the send window. Blasting your whole list at 9:00 a.m. is a pattern; trickling over hours looks human.
  • Stop on reply. Continuing a sequence after someone replies invites complaints — the fastest way to wreck reputation.

The scalable answer isn't a bigger number per inbox — it's more inboxes across more warmed domains, each sending a safe, human amount.

The 15-minute fix checklist

Work top to bottom. The order matters — authentication gates everything below it.

  1. SPF, DKIM, DMARC all present and aligned to your From domain. (Check it free.)
  2. Domain not blacklisted (Spamhaus, SURBL) and older than ~4 weeks.
  3. Warmup running on every sending mailbox — no cold domain sending real volume.
  4. List verified, zero purchased contacts, bounce rate under 2%.
  5. Complaint rate under 0.3% — if higher, cut volume and audit targeting now.
  6. Open tracking off, link tracking minimal and on a clean domain.
  7. Copy scored for trigger words and link/image bloat. (Scan it free.)
  8. Volume capped at ~20–40/mailbox/day, ramped gradually, stop-on-reply enabled.

If you tick all eight and still land in spam, the problem is almost always reputation that needs time to recover — pull volume back for two to four weeks and let warmup rebuild trust.

The real problem: you find out too late

For anyone running more than one domain or client, the genuinely hard part is timing: you don't find out you're in spam until your reply rate has already cratered. A sudden drop in open rate is often the first visible signal — the cold email open rate dropped guide covers how to diagnose whether it's a spam placement issue or something else. By then you've burned days of sends into the void.

ColdOps was built for exactly this blind spot. It watches every sending domain and mailbox across your Instantly, Smartlead, and EmailBison workspaces and flags a broken SPF record, a stalled warmup, or a bounce spike the moment a sync catches it — then emails you before your clients notice. Deliverability problems are cheap to fix and expensive to ignore; the whole game is catching them early.

Start with the checklist above and the free deliverability checker. Land in the inbox first — everything else in cold email depends on it.

Frequently asked

Why are my cold emails suddenly going to spam?
A sudden drop almost always traces to one change: a new sending domain that isn't warmed, a broken SPF/DKIM/DMARC record, a spike in volume, or a spam-trap hit from a stale list. Check what changed in the last 7–14 days first — deliverability problems are rarely random.
How do I know if my cold emails are landing in spam?
Run a seed/placement test: send to a set of Google, Outlook, and Yahoo test inboxes and see where each lands. Most sending tools (including Instantly) have inbox-placement tests built in. Reply rate dropping while sends stay flat is the leading real-world signal.
How long does it take to fix cold email deliverability?
Fixing authentication is same-day. Rebuilding sender reputation after spam complaints or a blacklist takes 2–4 weeks of reduced volume and warmup. There is no instant fix for reputation — it's earned back by sending wanted mail slowly.
Does one spam complaint ruin my domain?
No — but complaint rate matters. Google and Yahoo want you under 0.3% and ideally below 0.1%. One complaint on low volume is noise; a sustained rate above 0.3% will push you to spam across the whole domain.

Keep reading