The Short Answer
Mail goes to spam for three reasons: the receiver cannot prove the message is yours, the domain or IP that sent it has a bad track record, or enough recipients have hit the junk button on similar mail. If your own business mail has started landing in junk, work through these in order:
- Authentication: SPF, DKIM, and DMARC all pass, and at least one of the first two lines up with your From domain.
- Every sender: the website, the invoicing tool, the helpdesk, and the newsletter service are all covered by those records.
- Complaints: Google asks senders to keep the spam rate shown in Postmaster Tools below 0.3 percent.
- Blocklists: look up the domain and each sending IP, but only after the first three.
Why the Mail Is Being Filtered
This article is for the person who owns a domain, can edit its DNS, and has noticed that customer replies, form notifications, invoices, or password resets are turning up in junk. The first half explains the causes in roughly the order a receiving server weighs them. The second half gives the order in which you should check them, and the two orders are different on purpose.
Authentication is the one cause you can repair in an afternoon. It is also where most small domains turn out to be losing.
Authentication Is the First Question a Receiver Asks
Before a filter wonders whether your message is wanted, it asks whether the message is yours. Three records answer that. SPF lists the servers allowed to send for your domain. DKIM puts a cryptographic signature inside each message. DMARC tells the receiver what to do when neither of the other two matches the domain the recipient sees in the From line.
Google’s sender requirements ask every sender for SPF or DKIM, valid forward and reverse DNS on the sending IPs, a TLS connection, and messages formatted to RFC 5322 (September 2026). Missing one does not send you to junk automatically. It takes away the cheapest evidence in your favor and leaves the verdict to whatever else the filter knows about you.
Gmail and Outlook.com Publish Requirements With Numbers in Them
Past a certain volume, advice turns into a rule. Google’s list for senders of 5,000 or more messages a day to personal Gmail accounts asks for SPF and DKIM together, a published DMARC record (a policy of none is enough), alignment between the From domain and the domain that passed SPF or DKIM, and one-click unsubscribe on marketing and subscribed mail.
Microsoft enforces a similar rule and tells you when you break it. A sender of 5,000 or more messages that uses one domain and has not met the requirements gets the bounce 550 5.7.515, which reads “Access denied, sending domain does not meet the required authentication level.” Microsoft’s fix is SPF and DKIM passing, plus a DMARC record such as v=DMARC1; p=none with alignment. If that code is in your bounce messages, you have your diagnosis, and the remaining sections are the repair instructions.
A Spam Rate Above 0.3 Percent Already Counts Against You
Google asks senders to keep the spam rate reported in Postmaster Tools below 0.3 percent. That is three complaints per thousand messages, a lower line than most people would guess, and you cannot estimate it from the outside.
Postmaster Tools holds that figure along with domain and IP reputation, authentication results, and delivery errors. It has one catch: data can be missing when the daily message count is too low, which Google does to protect user privacy. A shop that sends a few hundred messages a day may open the dashboard and find nothing. That is why small senders so often end up diagnosing this blind.

Your Website Is Usually the Unauthorized Sender
Almost every site sends mail: contact form notifications, order receipts, password resets, admin alerts. A WordPress site left at its defaults hands all of that to the web server’s built-in mailer. The message leaves from the hosting IP, carries a From address at your domain, and has no DKIM signature.
Those messages are genuinely yours, and they fail authentication anyway. They fill the failing bucket in a DMARC report more often than any other source, and they teach receivers that your domain sometimes sends unsigned mail, which hurts the messages you did set up properly. Sending them through a real path fixes it at the source. Either Email Delivery for Cloudflare or a transactional email service will do that.
One-Click Unsubscribe Is a Pair of Headers, Not a Footer Link
The unsubscribe link at the bottom of your newsletter does not meet the requirement. RFC 8058 defines two headers instead: List-Unsubscribe-Post: List-Unsubscribe=One-Click, and a List-Unsubscribe header that must carry one HTTPS URI.
When a subscriber taps the unsubscribe button in their mail app, the receiving system sends an HTTPS POST to that URI with the key and value from the first header. The specification is firm on one detail: the sender must not answer with an HTTPS redirect, because redirected POST requests have historically not worked reliably. A click-tracking redirect sitting in front of your unsubscribe endpoint can therefore break it without any error on your side.
Spam Traps and the List Nobody Has Cleaned
A spam trap is an address that exists to catch people who mail without permission. Some are old mailboxes that a provider recycled into traps, so a list you collected honestly years ago can turn into a liability. Others never belonged to a person and were planted where a scraper would find them, which means any mail that reaches them shows how the address was obtained.
You cannot spot a trap by looking, and nobody will tell you which address it was. You can stop mailing anyone who has not opened a message in a year, and you can refuse to import a list you did not collect yourself. Heavy bounces and trap hits tend to arrive together, so a list that bounces badly is usually hitting traps too.
Domain Reputation and IP Reputation Are Separate Scores
The domain’s reputation follows your domain wherever you send from. The IP’s reputation belongs to the machine, and on a shared sending IP part of it belongs to strangers.
That difference decides whether a migration helps. Switching email providers gives you a new IP and leaves the domain’s history exactly where it was. If the domain is the problem, a new IP buys a few good days before the same filtering returns. If the IP is the problem, the move is the right fix. Work out which one it is before you migrate anything.
Working Through It in the Order That Finds the Cause Fastest
The causes above are not equally common, and checking them in the order they were explained wastes time. This sequence puts the answer in front of you soonest, and most domains find it by step three.

Start with One Message That Landed in Junk
Pull up one specific message that went to spam and open its full headers. In Gmail that is Show original; in Outlook it is the message source. Search the text for Authentication-Results. A healthy one looks like dkim=pass header.i=@example.com; spf=pass smtp.mailfrom=example.com; dmarc=pass (p=NONE) header.from=example.com.
Three passes mean authentication is fine, so the trouble is reputation or content and you can skip ahead. A fail, or a none, on any of the three names the exact record to go and read. This single line replaces a lot of guessing, and it costs nothing.
Read the Record a Receiver Resolved, Not the One You Think You Published
The DNS you edited and the DNS the world sees are not always the same. The usual culprits are a typo, a record added at the wrong host, a DNS provider that splits long TXT records badly, and a change that has not propagated yet.
Your own DMARC reports are the quickest check, because the policy_published block in each one is a receiver reading your record back to you. Reading a DMARC report goes through those files field by field. If you have no reports yet, run dig +short TXT example.com and dig +short TXT selector._domainkey.example.com from a machine outside your network and compare the output to what you meant to publish.
Count Your Senders Before You Touch the SPF Record
SPF has a hard limit that is easy to cross and shows no obvious symptom. RFC 7208 caps the DNS-querying terms at ten during evaluation, counting include, a, mx, ptr, and exists, plus the redirect modifier. Go over and the evaluator must return permerror, which is not a pass.
Every vendor you add brings at least one include, and a single include can fan out into several more lookups inside itself. A record with six vendor includes may already be over the line. A second limit applies to void lookups, the queries that return no answer or a name error: more than two also produces permerror. How an SPF record is built covers the syntax and the counting in detail.
Sign Every Sender With DKIM, Including the Forgotten Ones
After SPF, sign everything. A DKIM signature travels inside the message and usually survives a plain forward. SPF stops helping the moment someone forwards your mail from their own server.
Each service that sends as you needs its own key at its own selector: the mailbox provider, the marketing platform, the helpdesk, the invoicing system, the website. Alignment defaults to relaxed for both SPF and DKIM, so a signature from mail.example.com still matches a From address at example.com, and that is what makes subdomains workable. What fails to align is a vendor signing with its own domain. The raw results show a DKIM pass, and the DMARC verdict shows a DKIM fail. DMARC alignment and how to fix a misaligned sender walks through the repair.

Only Then Check Whether You Are Listed Somewhere
Most people check blocklists first, and they are rarely the answer, which is why they sit this far down. When a listing is the cause, it is usually the whole cause, and mail gets refused outright instead of being filed in junk.
Look up your sending domain and every sending IP against the major lists. A listing that appeared the week the filtering began is your answer. One that has sat there for months while mail arrived normally probably is not. Write down the date either way, because a delisting request nearly always asks what changed.
Content and Volume Come Last and Matter Least
Most online advice lives here: subject lines, image ratios, the word “free.” None of it is wrong. It is just worth little next to everything above, and rewriting your copy while DKIM is broken is wasted effort.
Two content problems are structural rather than stylistic. A link shortener in the body puts a domain with someone else’s reputation into your message. And a sudden jump in volume, such as a quiet domain sending its first big campaign, looks like a compromised account to a receiver with no history to compare against. If you plan to send far more than usual, build up over a couple of weeks instead of one morning.
When Everything Passes and Mail Still Goes to Junk
It happens, and it marks the point where the problem stops being a record and becomes a pattern. Authentication proves the mail is yours. It says nothing about whether recipients want it, and a decision built on complaint history will not yield to a DNS change.
What helps is unglamorous. Mail people who asked for it, drop anyone who has not engaged in a year, keep the volume steady, and make unsubscribing easy enough that nobody reaches for the junk button instead. Then watch the numbers rather than your own inbox, because by the time you notice personally it has usually been going on for weeks.
Watching it for you is what Deliverability Monitoring exists to do. We check the major blocklists every day for your domain and your sending addresses, track your sending reputation against your own baseline rather than a generic benchmark, and tell you the day something changes instead of at the end of the month. When a listing appears we name the cause rather than the symptom, handle the delisting ourselves, and check again until it clears. Nothing is installed and we never see your mailboxes. Every check is kept for 90 days, so you can show exactly when a listing started and when it cleared. It is not inbox placement testing, which needs a seed-list vendor, and we do not pretend to offer that.
The other half is the records themselves. Email Authentication proves the mail is yours, and Deliverability Monitoring watches whether it is arriving; they solve different halves of the same problem, and a domain with filtering trouble usually needs both. If you are weighing this against a tool you would run yourself, the deliverability comparisons take the main options in turn. And if the hard part is that nobody is sure who controls the zone you need to edit, that is a DNS problem before it is an email one, and the walk through DNS record types is a reasonable place to start.









