InboxRatio
Check your domain

Why are my emails going to spam? The seven causes, in checking order

The campaign went out Tuesday morning. Open rates came back at a third of normal, replies stopped, and a customer forwarded you a screenshot of your own newsletter sitting in their junk folder. Nothing about the send felt different — same list, same template, same time of day. So why did the mailbox providers suddenly decide you're spam?

The honest answer: they didn't decide suddenly. Spam placement is almost always the visible end of a problem that has been accumulating quietly — an authentication record that was never quite right, a list that aged past its useful life, a reputation that slid a little with every send. The good news is that the causes are finite, they leave evidence, and they can be checked in a specific order.

This is the diagnostic article. If you want the step-by-step repair plan once you know your cause, that's a separate guide. And if you'd rather answer a few questions and be routed straight to your likely cause, our deliverability troubleshooter walks the same tree interactively.

Before anything else: establish where you stand

Guessing at causes wastes weeks. Two checks take ten minutes and rule out half the possibilities.

First, run your sending domain through the email deliverability score. It reads your DNS the way a receiving server does and scores the setup side of your deliverability: SPF present and valid, DKIM resolvable, DMARC published, MX and reverse DNS sane. A configuration problem shows up here immediately, and configuration problems are the single most common cause of sudden spam placement.

Second, send a real message from your platform to a mailbox you control, open the raw source, and paste it into the email header analyzer. The Authentication-Results header shows you exactly what the receiver concluded: spf=pass, dkim=fail, dmarc=pass and so on. This is the ground truth. Marketing dashboards summarize; headers don't.

With those two results in hand, work down the list.

Cause 1: authentication is missing or broken

Mailbox providers have spent the last few years converting authentication from a best practice into an entry requirement. Google's bulk sender guidelines require senders of roughly 5,000 or more messages a day to Gmail addresses to authenticate with SPF, DKIM and a published DMARC policy; Yahoo's sender requirements mirror them. Below that volume the rules are softer, but unauthenticated mail is filtered more aggressively at every scale.

The failure modes we see most:

  • No DKIM signature for your own domain. Your platform signs with its domain instead of yours, so the signature exists but does nothing for your identity. Check the d= value in the header analyzer output.
  • SPF record errors. Two SPF records on one domain (a permanent error), a missing include for your sending platform, or a record that exceeds the 10-DNS-lookup limit. Two minutes in the SPF checker finds all three.
  • No DMARC record at all. Even p=none satisfies the letter of the bulk sender requirements. Absence does not.

The email authentication checker runs all of these against your domain in one pass. If anything fails there, stop reading and fix it first — nothing further down this list matters while authentication is broken.

Cause 2: your domain reputation has slipped

Domain reputation is the memory mailbox providers keep about your domain: how recipients have historically reacted to your mail. It moves slowly in both directions, which is exactly why spam placement feels sudden — the score crossed a threshold, but the slide started months earlier.

Reputation damage usually traces to one of the later causes on this list (complaints, bad list hygiene, spam traps), so treat it as a symptom with its own momentum. The practical consequence: even after you fix the root cause, placement recovers on the provider's schedule, not yours. Google Postmaster Tools shows a domain reputation band for mail sent to Gmail; if yours reads "low" or "bad", you have confirmation that this is a reputation problem and not a configuration one.

Cause 3: the IP you send from has a problem

Most senders on marketing platforms share sending IPs with hundreds of other customers. Shared pools are fine — platforms police them — but IP reputation is still a real input, and a pool neighbor's bad week can bleed into your results. If your domain checks out clean but placement dropped across all your mail at once, ask your platform which pool you're in and whether it has had recent listing issues.

Senders on a dedicated IP own the opposite problem: the reputation is entirely theirs, including the damage from volume gaps and spikes. A dedicated IP that sat idle for six weeks and then sent 200,000 messages behaves, from the receiver's point of view, like a hijacked server.

Cause 4: your list is the problem

This is the cause people check last and should check first. Lists decay: people change jobs, abandon mailboxes, forget they subscribed. Sending to a stale list produces exactly the signals filters are trained on — high bounce rates, zero engagement, and hits on recycled spam traps, addresses providers resurrect specifically to catch senders who don't clean their data.

Purchased or scraped lists are a special case: they concentrate every one of those signals into a single send, which is why one purchased list can undo a year of careful sending. There is no filter-side trick around this, and we don't publish evasion advice — the fix is consent-based collection and regular removal of non-engagers.

Cause 5: recipients are marking you as spam

The complaint rate — the share of delivered mail that recipients report as spam — is the most direct signal a mailbox provider has, because it's a human saying "I didn't want this." Google's Postmaster Tools documentation sets the line explicitly: keep the user-reported spam rate below 0.3%, and ideally under 0.1%. Cross it repeatedly and bulk-folder placement follows.

Complaints spike for mundane reasons: an unsubscribe link that's hard to find (people report instead of hunting), a sudden change in frequency, a subject line that doesn't match the content, or mailing people who signed up so long ago they no longer remember you. If you send to Gmail at volume, Postmaster Tools shows your measured rate; treat any upward trend as urgent.

Cause 6: content — a smaller factor than you think

Content is the cause everyone suspects first and is the real culprit least often. Modern filters weigh sender reputation and recipient behavior far more heavily than trigger words. That said, content still matters at the margins: image-only emails with no text, link shorteners, mismatched link text and destinations, and sloppy HTML all add weight to the wrong side of the scale. A message that looks like phishing gets treated like phishing, whoever sent it.

If your authentication passes, your reputation metrics look healthy, and placement still disappoints, run controlled content tests — one variable at a time, same segment, same send window. Anything less rigorous will have you chasing ghosts.

Cause 7: you changed something — volume, domain, or platform

Filters model your normal. New domain, new IP, a platform migration, or a holiday-season volume spike all break the model, and unfamiliar behavior gets filtered defensively until a new track record accumulates. This is the entire logic behind warming up a domain: ramping volume gradually so each send extends a pattern instead of violating one.

If your spam problem started within a few weeks of a migration or a big volume change, you likely don't have a reputation disease — you have a history deficit, and the treatment is patience plus consistent sending to your most engaged segment.

Working the diagnosis

The order above is the checking order for a reason: each cause is roughly as common as it is cheap to verify. Authentication takes minutes to check and fails constantly. List and complaint problems take a report review. Content testing takes weeks — do it last.

Three habits make the diagnosis stick. Read your Authentication-Results headers whenever something changes, not just during a crisis. Register for Google Postmaster Tools before you need it, because it only accumulates data going forward. And re-run the checks after every platform or DNS change, since that's when working setups quietly break.

Related guides

About this guide

Written by InboxRatio Editorial, the team that runs controlled inbox placement tests across the email platforms we review. This guide draws on the failure patterns we observe in that testing and in the DNS configurations submitted to our free tools. It contains no vendor sponsorship and no affiliate influence on its recommendations.

Methodology

InboxRatio measures deliverability by sending real campaigns through each platform to a controlled seed list and recording where every message lands. The diagnostic order in this guide reflects what that testing shows about which failures are common and which are rare. The full protocol is documented in how we test, and our source rules in sources.

Last updated

21 August 2026. Diagnostic order and provider requirements are reviewed quarterly against current Google and Yahoo sender documentation.

Frequently asked questions

Why are my emails suddenly going to spam when nothing changed? Usually something did change, just not on your side: a reputation metric crossed a threshold after a long slide, a shared IP pool picked up a bad neighbor, or a provider tightened enforcement. Check authentication first, then complaint and engagement trends over the past quarter, not just the past week.

Do words like "free" or "sale" send email to spam? Not on their own. Modern filters are driven by sender reputation and recipient behavior; individual words carry little weight. A trusted sender can write "FREE!!!" and reach the inbox; a distrusted one gets filtered writing plain prose. Fix reputation before rewriting copy.

How do I check if my emails are going to spam? Send to mailboxes you control at Gmail, Outlook and Yahoo and look. For the configuration side, run the email deliverability score. For Gmail-specific reputation and spam-rate data, register your domain with Google Postmaster Tools.

Will fixing SPF, DKIM and DMARC get me out of the spam folder? If authentication failure was the cause, placement typically recovers within days. If the underlying issue is reputation or list quality, authentication is necessary but not sufficient — it removes one reason to filter you while the reputation repair proceeds on its own timescale.

How long does it take to recover from spam placement? Configuration fixes can show results in days. Reputation recovery is slower — typically weeks of consistent, well-received sending to your most engaged recipients. No one reputable can promise a date; the mailbox providers publish direction, not timelines.

Does the spam folder mean my domain is blacklisted? Not necessarily. Public blocklists mostly affect IP-level rejection at smaller receivers; Gmail and Microsoft rely primarily on their own internal reputation systems. Spam-folder placement at a major provider usually reflects their internal scoring, not a public list.

Diagnose in checking order — authentication, reputation, list, complaints, content, change history — and confirm each step with evidence from headers and postmaster data rather than intuition. Start now by running your domain through the email authentication checker; it clears or convicts the most common cause in under a minute.