Why are my emails going to spam?
Cold email lands in spam for eight common reasons - failed authentication, a cold domain, bad list quality, spam complaints, and more. Diagnose yours here.
Cold email lands in spam for eight common reasons. In rough order of frequency: email authentication isn't resolving, the sending domain is too new, list quality is producing bounces, recipients are complaining, volume ramped too fast, the domain or IP is blocklisted, engagement is too low, or the content pattern looks like spam. Work through them in that order — authentication is both the most common cause and the fastest to fix.
Who this applies to: anyone sending outbound email through Alice. Start with the domain health checker — it tests several of these causes at once.
Diagnose it first
Before changing anything, run these checks. They take five minutes and will tell you which of the eight causes you actually have.
| Check | Tool | What a failure means |
|---|---|---|
| Everything at once | Domain health checker | Start here |
| SPF resolves | SPF record checker | Cause 1 |
| DKIM signs validly | DKIM checker | Cause 1 |
| DMARC policy exists | DMARC checker | Cause 1 |
| Not blocklisted | Email blacklist checker | Cause 6 |
| Gmail reputation | Google Postmaster health check | Causes 4, 7 |
| Mail routing correct | MX record checker | Configuration error |
Then open mailbox health in 11x analytics. Deliverability problems are often isolated to one mailbox that's dragging the whole domain down.
Cause 1 — Authentication isn't resolving
The most common cause by a wide margin. SPF, DKIM, and DMARC must all resolve for your sending domain. Adding the DNS records isn't the same as them working — typos, wrong hostnames, multiple conflicting SPF records, and un-propagated changes are all routine.
A domain can have all three records present and still fail authentication. Verify each one with the checkers above rather than trusting that you pasted them correctly.
Fix: see Set up SPF, DKIM, and DMARC. Fixed within hours once DNS propagates.
Cause 2 — The sending domain is too new
A new domain has no sending reputation. Mailbox providers treat sudden volume from an unknown domain as a spam signal, and there's no history to weigh against it.
Fix: warm the domain up — ramp volume gradually rather than starting at target rate. See How to warm up a new sending domain. Takes weeks, not hours.
Cause 3 — List quality is producing bounces
A high bounce rate is a direct reputation signal. Invalid addresses, catch-all domains, and stale contact data all contribute.
Fix:
- Let Alice source contacts from the verified database rather than uploading unvalidated lists
- Remove any list you can't vouch for the age of
- Enable the Qualification Agent so out-of-profile prospects never get sent to in the first place
Cause 4 — Recipients are complaining
Spam complaints are the most damaging signal there is. They usually mean you're reaching people who aren't remotely in your market, not that your copy is bad.
Fix: tighten your ICP before you touch your copy. A well-targeted mediocre email outperforms a brilliant email sent to the wrong person. See Set up Alice → define your ICP.
Cause 5 — Volume ramped too fast
A sharp increase in send volume looks like a compromised account, even on a domain with good history.
Fix: let the Deliverability Engine pace volume. If you've increased volume manually, drop back to the previous level and ramp more gradually.
Cause 6 — The domain or IP is blocklisted
Check with the blacklist checker. Blocklisting is usually the consequence of causes 3, 4, or 5 rather than an independent problem.
Fix: resolve the underlying cause first, then request delisting. Delisting without fixing the cause gets you relisted.
Cause 7 — Engagement is too low
Mailbox providers weigh opens, replies, and positive actions. Mail that nobody engages with gradually stops reaching inboxes even without complaints.
Fix: improve relevance rather than volume. This is a knowledge base and ICP problem — see Set up Alice → build the knowledge base. Thin inputs produce generic messages, and generic messages don't get replies.
Cause 8 — Content and link patterns
Less influential than most people assume, but it still matters at the margin: heavy link counts, link shorteners, large images, tracking-heavy templates, and attachments in a first touch.
Fix: keep first-touch emails plain and text-forward. Avoid shorteners entirely.
Fix them in this order
Verify authentication
SPF, DKIM, DMARC. Fastest fix, most common cause.
Check per-mailbox health
Isolate whether it's the domain or one bad mailbox.
Pause and assess if complaints are high
Complaint-driven damage compounds. Stop sending before you diagnose further.
Tighten targeting
ICP and Qualification Agent. Addresses causes 3, 4, and 7 at once.
Reduce and re-ramp volume
Then rebuild gradually.
Request delisting last
Only after the underlying cause is fixed.
How long recovery takes
| Problem | Time to fix |
|---|---|
| Authentication misconfigured | Hours (DNS propagation) |
| Content or link patterns | Immediate, next send |
| Volume ramped too fast | Days |
| Blocklisting | Days to weeks after the cause is fixed |
| Reputation damage from complaints | Weeks of low-volume, high-engagement sending |
This asymmetry is why deliverability is a prevention discipline. Authentication takes an afternoon; reputation repair takes a quarter.
Next steps
Set up SPF, DKIM, DMARC
The authentication fix, step by step.
Warm up a new domain
Ramp a new domain safely.
Set up Alice
Domain, knowledge base, and ICP configuration.
Help Center
All support articles and tools.
Still need help
Email support@11x.ai with your sending domain, the results of the domain health check, and your current bounce and complaint rates.