Why your business email goes to spam: SPF, DKIM and DMARC in plain English
If your proposals land in the client’s spam folder, or never arrive at all, the cause is usually three DNS records on your domain: SPF, DKIM and DMARC. They prove to Gmail, Outlook and other providers that a message really came from your company. Without that proof, the provider gets suspicious.
The good news: you set them up once, they cost nothing in licenses, and you can check them yourself in a few minutes.
What each one does
| Record | What it does | Where it lives |
|---|---|---|
| SPF | Lists the servers allowed to send email for your domain | A TXT record on the domain |
| DKIM | Signs each message with a key only your email service holds | Records under _domainkey |
| DMARC | Tells receivers what to do with mail that fails SPF and DKIM, and asks for reports | A TXT record at _dmarc |
The three work together. SPF and DKIM do the checking; DMARC decides what happens when the check fails and confirms that the verified domain matches the one in the From line.
Why this started to matter so much
For years, authenticating email was a recommendation. It became a requirement:
- since February 2024, Gmail and Yahoo require SPF or DKIM from every sender, and all three records from anyone sending around 5,000 messages a day or more;
- since May 2025, Outlook.com (and Hotmail) applies the same rule to high-volume senders.
In practice even low-volume senders feel it: unauthenticated mail loses points with the filter and lands in spam more easily.
There’s a second reason that has nothing to do with delivery. Without DMARC, anyone can send an email that looks like it came from your domain. That’s the basis of fake-invoice fraud and the “our bank details have changed” scam. The FBI recorded $2.77 billion in business email compromise losses in 2024 alone.
How to check your domain in 5 minutes
The simplest test needs no tools:
- send an email from your work account to a Gmail account;
- open it in Gmail, click the three dots and choose Show original;
- look at the SPF, DKIM and DMARC lines at the top. Each one should say PASS.
If any says FAIL, or doesn’t show up, that’s where the problem is.
To see the published records, open a terminal (Command Prompt on Windows) and run these with your own domain:
nslookup -type=txt yourcompany.com
nslookup -type=txt _dmarc.yourcompany.com
The first should return a line starting with v=spf1. The second, one starting with v=DMARC1. If the second returns nothing, the domain has no DMARC.
Step 1: SPF
SPF is a TXT record at the root of the domain. If you only send through Microsoft 365:
v=spf1 include:spf.protection.outlook.com -all
If you only send through Google Workspace:
v=spf1 include:_spf.google.com ~all
Before you publish, list everything that sends email as your domain: the accounting or billing system that emails invoices, the newsletter tool, the website’s contact form, the scanner that emails PDFs. Each service tells you the include it needs in the record.
Three rules prevent most mistakes:
- Only one SPF record can exist. Two
v=spf1records on the same domain invalidate both. Merge them into one. - No more than 10 DNS lookups. Every
includecounts. Go over and SPF fails. - The ending sets how strict it is.
~allmarks mail from outside the list as suspicious;-allfails it. Start with~allif you’re unsure of the list and move to-allonce you are.
Step 2: DKIM
DKIM has to be turned on in your email service and published in DNS.
In Microsoft 365: at security.microsoft.com, go to Threat policies, Email authentication settings, DKIM. Select the domain, copy the two CNAME records the portal shows (selector1._domainkey and selector2._domainkey), publish them in DNS and enable signing.
One detail trips people up: without this step, Microsoft 365 already signs your mail, but with an onmicrosoft.com domain that isn’t yours. The signature exists and DMARC still fails, because the domains don’t match.
In Google Workspace: in the Admin console, go to Apps, Google Workspace, Gmail, Authenticate email. Generate the key, publish the TXT record at google._domainkey and click “Start authentication.”
Step 3: DMARC, in three stages
DMARC is a TXT record at _dmarc.yourcompany.com. Start by just watching:
v=DMARC1; p=none; rua=mailto:[email protected]
With p=none nothing is blocked. Providers start sending daily reports to the rua address, showing who is sending as your domain and whether it passes. The reports arrive as XML; DMARC report readers, several with a free tier, turn them into something readable.
Then go in this order:
- Watch for two to four weeks. Look for legitimate services that are failing (the system you forgot in SPF) and fix them.
- Move to
p=quarantine. Mail that fails goes to the recipient’s spam folder. - Get to
p=reject. Forged mail is refused. This is where your domain is actually protected.
The mistakes that show up most
- Stopping at
p=none. The record exists, the testing tool turns green and the domain is still unprotected. - Forgetting a sender. Invoices go out through a system nobody added to SPF and start landing in spam once DMARC is enforced.
- Switching providers and keeping the old SPF. The record keeps authorizing a service you no longer use.
- Ignoring domains that don’t send email. A parked domain can be spoofed too. Give it
v=spf1 -alland a DMARC record withp=reject.
What authentication doesn’t fix
SPF, DKIM and DMARC prove who sent a message. They don’t say whether it’s wanted. Google, for example, asks senders to keep the rate of messages reported as spam below 0.3%. Purchased lists, bulk mail with no unsubscribe link and clickbait subject lines will sink the reputation of a fully authenticated domain.
Where to start
Run the Gmail test today. If all three show PASS and your DMARC isn’t at p=none, your domain is in good shape. If something fails, follow the steps in order: SPF, DKIM, DMARC.
If your mail runs on Microsoft 365, review the 7 security settings most companies miss while you’re in there. And if nobody on your team owns this, see how nearshore IT support works.
Setting up and watching your company’s email is part of our managed IT plans. For a first look at your situation, the free online assessment takes a few minutes.
Questions
Does DMARC with p=none protect my domain?
No. With p=none the receiver only sends reports and delivers the message normally, even when it's forged. Protection starts at p=quarantine, which sends forged mail to spam, and is complete at p=reject, which refuses it.
Do I need this if we only send a few emails?
Yes. Gmail asks every sender for SPF or DKIM, not just bulk senders. And spoofing protection doesn't depend on volume: it takes one scammer using your domain once for a client to pay a fake invoice.
Can changing these records break my email?
A wrong SPF record can, because it starts failing legitimate mail. That's why order matters: list every service that sends for your domain before you publish SPF, and start DMARC at p=none, which blocks nothing.
How long until it takes effect?
The records apply within minutes or hours of being published. The full path to DMARC at reject takes a few weeks, because you need to watch the reports before tightening the policy.
Everything passes and we still land in spam. Now what?
Authentication is a requirement, not a guarantee. After it, what counts is the reputation of your domain and server, the content of the message and how recipients react. Purchased lists and bulk mail with no unsubscribe option ruin reputation even with everything authenticated.