The first thing worth understanding: it is not your wording. Most people look for the cause in the writing — "I must have put FREE in capitals" — when almost always the problem is that the receiving server cannot verify the email is really yours, and when in doubt it sets it aside.
That "verifying" depends on three technical records that live in your domain. Five of the seven causes on this list are failures in them. Let's go in order.
1. Your domain doesn't say who may send for it
This is the SPF record: the list of servers authorised to send email on behalf of your company. If it doesn't exist, any server in the world can claim to be you, and receivers know it — so they distrust every one of them, yours included.
How to tell if it's yours: it is one of the things the free checker spots in seconds. If it comes back "no SPF", this is your cause and probably not the only one.
2. You have SPF, but it is broken without showing it
This is the most treacherous of them all. SPF has a limit of ten lookups, and every service you add eats into that budget. Once you go over, the receiving server treats your domain as if you had no SPF at all, even though the record looks flawless.
It arrives by accumulation: you signed up for a campaign tool, then a CRM, then the invoicing system. Nobody connects the day the email stopped arriving with the provider added three months earlier.
How to tell if it's yours: you have to resolve the whole chain, not just look at the record. We explain it in depth here, with measurements of large Mexican brands — two are at the exact limit.
3. Your email goes out unsigned
DKIM is a cryptographic signature proving the message came from you and that nobody modified it along the way. Without it, your email arrives with no credential: not an automatic reason for spam, but it counts against you while the receiver is deciding.
How to tell if it's yours: it is the hardest to check from outside, because the signature is published under a name each provider chooses. No tool can state with certainty that you don't have it — only that it didn't find it where it usually lives. You confirm it by reviewing the settings of every platform that sends email as you.
4. You published DMARC but it is in observation mode
DMARC is the instruction for what to do when something doesn't add up. Many companies publish it on p=none, which reports but does not block, and there they stay. The domain "has DMARC" on the inventory and protects nothing.
How to tell if it's yours: the checker gives you the exact policy. If it says p=none, you are observing the problem, not solving it — the detail is here.
5. Someone sends for you without aligning with your domain
The typical case: you hire an invoicing or campaign platform. They send from their server but put your company's name in the sender. Technically the email passes the provider's checks, and fails yours, because the domain that was verified doesn't match the one the client sees.
It is the most frustrating cause, because your normal email arrives fine and only the invoices go to spam, or only the campaigns.
How to tell if it's yours: it is invisible if you only inspect records. It shows up in DMARC reports after several days of collection, or by sending test email from each platform and seeing where each one lands.
6. The IP you send from has a bad reputation
If you share a server with other customers — normal on shared hosting and at many agencies — you inherit their behaviour. It only takes one neighbour sending campaigns to purchased lists for the IP to land on a blacklist and your email to go with it.
How to tell if it's yours: you look up the status of your domain and your IP on lists such as Spamhaus. It is part of the full audit.
7. Yes, sometimes it is the content
It comes last because it is almost never the main cause, but it exists: shortened links, executable attachments, a single block of image with no text, or blasting a list you bought. If the six points above are in order and you still land in spam, this is where to look.
How to tell if it's yours: if your normal email arrives fine and only the bulk sends go to spam, the problem is in how you send, not in how you are configured.
Start by finding out which of the seven it is
The checker verifies causes 1, 2 and 4 in seconds, which together explain most cases. It asks for no sign-up and no access to anything.
Why this isn't fixed by "writing better"
There is a lot of advice going around about avoiding certain words or not using capitals. It isn't false, it just addresses cause number seven when the problem is usually in the first five. You could rewrite your emails for a whole year and nothing would change if your domain cannot prove you are you.
The good news is that the first five are configuration: you fix them once, they stay fixed, and they don't depend on anyone remembering anything while writing.
Keep reading
- SPF, DKIM and DMARC explained without jargon The three records behind five of the seven causes.
- The 10-lookup SPF limit Cause number 2, with measurements of Mexican brands.
- Your DMARC on p=none is not protecting you Cause number 4, and why so many stop halfway.