SPF, DKIM and DMARC are three DNS records that prove your emails really come from your domain. SPF lists the servers allowed to send for you, DKIM adds a digital signature to each message, and DMARC tells inboxes what to do when a check fails. Without all three, Gmail and Outlook often send your mail to spam.
Why Are Your Business Emails Going to Spam?
You send a quote to a new client. They never reply. A week later they tell you it was sitting in their junk folder the whole time.
This happens to small businesses every day, and the cause is usually not the wording of the email. It is missing or broken email authentication on the domain.
Inbox providers like Gmail, Outlook.com and Yahoo Mail receive enormous amounts of spoofed mail, where criminals pretend to be a real company. To protect users, they check every incoming message for proof that the sender is legitimate. If your domain cannot provide that proof, your messages look exactly like a forgery.
The good news is that the fix is a handful of DNS records. Once you understand what each one does, setting them up takes far less time than most people expect.
What Is Email Authentication?
Email authentication is a set of DNS based checks that let receiving mail servers confirm a message was sent by someone authorized to use your domain name.
Email was designed in an era when nobody expected abuse. The original protocol, SMTP, lets anyone type any address into the “From” line. Authentication standards were added later to close that gap.
There are three standards that work together:
| Record | Full Name | What It Proves | Simple Analogy |
|---|---|---|---|
| SPF | Sender Policy Framework | The sending server is on your approved list | A guest list at the door |
| DKIM | DomainKeys Identified Mail | The message was signed by your domain and not altered | A wax seal on a letter |
| DMARC | Domain based Message Authentication, Reporting and Conformance | The visible From address matches what SPF or DKIM verified, and what to do if it fails | The security guard’s instructions |
Each one is published as a record in your domain’s DNS, the same place your website’s A record and your MX records live.
What Is SPF and How Does It Work?
SPF is a DNS TXT record that lists every server and service allowed to send email using your domain. When a message arrives, the receiving server checks whether the sending IP address appears on that list.
A typical SPF record looks like this:
v=spf1 include:_spf.google.com include:servers.mcsv.net ~all
Here is what each part means:
- v=spf1 identifies the record as SPF.
- include: pulls in the approved servers of a service you use, such as Google Workspace or Mailchimp.
- ~all is a soft fail. It tells receivers that anything not listed is suspicious but should not be rejected outright.
A stricter version uses a minus sign in place of the tilde before “all,” which tells receivers to reject unlisted senders. Most businesses start with the soft fail and tighten later.
What Are the Limits of SPF?
SPF has two well known limits that cause real problems:
- Only one SPF record per domain. If you publish two, both can fail. Add new services to the existing record instead.
- A maximum of 10 DNS lookups. The SPF specification (RFC 7208) caps the number of lookups. Every include counts, and some includes contain their own nested lookups. Go over the limit and SPF returns an error.
SPF also breaks when email is forwarded, because the forwarding server is not on your list. That is one reason SPF alone is not enough.
What Is DKIM and Why Does It Matter?
DKIM adds an encrypted signature to the header of every email you send. The receiving server uses a public key published in your DNS to verify that signature, which proves the message came from your domain and was not changed in transit.
DKIM uses a pair of keys:
- A private key stays on your mail server or with your email provider and signs outgoing messages.
- A public key is published in DNS under a name called a selector, for example
google._domainkey.yourdomain.com.
You rarely write a DKIM record by hand. Google Workspace, Microsoft 365 and most email platforms generate the key for you. Your job is to copy it into DNS and then switch signing on inside the provider’s admin panel.
That last step is where many businesses get stuck. They add the DNS record but never click “Start authentication” in Google Workspace or enable DKIM in the Microsoft Defender portal, so messages go out unsigned.
Unlike SPF, a DKIM signature survives most forwarding, which makes it the more reliable of the two.
What Is DMARC and What Policy Should You Use?
DMARC ties SPF and DKIM together. It checks that the domain in the visible From address matches the domain that passed SPF or DKIM, a concept called alignment. It also tells receiving servers how to handle mail that fails and where to send reports.
A starter DMARC record is published at _dmarc.yourdomain.com and looks like this:
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
The p tag sets the policy. There are three options:
| Policy | What Happens to Failing Mail | When to Use It |
|---|---|---|
| p=none | Delivered normally, reports are sent to you | First few weeks, while you find every service sending as you |
| p=quarantine | Sent to spam or junk | Once reports show your legitimate mail is passing |
| p=reject | Blocked completely | Final stage, strongest protection against spoofing |
The rua tag is the address that receives daily aggregate reports in XML format. These reports show every server that sent mail claiming to be your domain, including ones you forgot about and ones you never authorized.
Why Does Alignment Matter?
Alignment is the part most guides skip. A message can pass SPF using your email marketing platform’s own domain while showing your domain in the From line. SPF passes, but it is not aligned, so DMARC still fails.
That is why setting up custom DKIM signing for each sending service, using your own domain, is so important.
Are SPF, DKIM and DMARC Required Now?
For high volume senders, yes. Google and Yahoo began enforcing new sender rules in February 2024, and Microsoft followed for Outlook.com, Hotmail.com and Live.com. Beginning May 5, 2025, Microsoft started rejecting bulk email that fails its requirements, which apply to large senders sending 5,000 or more emails per day.
Microsoft’s rules call for SPF, DKIM and a DMARC policy of at least p=none, aligned with either SPF or DKIM and preferably both. Google’s guidelines go further for bulk senders, also asking for one click unsubscribe on marketing mail and a low spam complaint rate.
If you send far fewer than 5,000 emails a day, these rules are not strictly mandatory for you. In practice, though, Gmail expects every sender to have at least SPF or DKIM, and authenticated mail consistently gets better treatment. Our view is simple: there is no good reason for a business domain to skip any of the three.
How to Set Up SPF, DKIM and DMARC Step by Step
The safest order is to list your senders, publish SPF, enable DKIM for each service, then add DMARC in monitoring mode. Here is how that looks in practice.
- List every service that sends email as your domain. Include your mailbox provider, newsletter tool, CRM, invoicing software, help desk, booking system and your website’s contact forms.
- Find your DNS manager. This is usually your hosting control panel (the Zone Editor in cPanel, for example) or your domain registrar.
- Create or update one SPF record. Add an include for each sending service and end with ~all.
- Turn on DKIM for each service. Copy the DKIM key each platform provides into DNS, then activate signing inside that platform.
- Publish DMARC at p=none with a reporting address you actually check.
- Send test emails to a Gmail and an Outlook.com account. Open the message, choose “Show original” in Gmail, and confirm SPF, DKIM and DMARC all show PASS.
- Review DMARC reports for two to four weeks. Free tools from providers like dmarcian or Postmark make the XML readable.
- Move to p=quarantine, then p=reject once every legitimate source passes.
DNS changes usually take effect within minutes to a few hours, though they can take up to 48 hours depending on your record’s TTL.
Real Example: A Small Business With Five Senders
Picture a dental office in Texas. Staff email from Microsoft 365, appointment reminders go through a scheduling platform, invoices come from QuickBooks, a monthly newsletter goes out through Mailchimp, and the WordPress site sends contact form alerts.
That is five different systems sending as one domain. If the SPF record only lists Microsoft 365, the other four fail SPF. If DKIM is only enabled in Microsoft 365, the newsletter and reminders fail DMARC alignment. Patients start reporting that reminders went to junk.
The fix was not a new email provider. It was one combined SPF record, DKIM keys for each platform, and a DMARC policy that started at p=none. Within a few weeks of reading reports, the office could safely move to quarantine.
What About WordPress Contact Form Emails?
WordPress sends email through PHP’s mail function by default, which often fails authentication. Many form plugins also set the From address to the visitor’s email, which your domain is not allowed to send as.
Two changes solve most of this:
- Use an SMTP plugin such as WP Mail SMTP to send through your real mailbox provider or a transactional service.
- Set the From address to an address on your own domain, and put the visitor’s email in the Reply To field instead.
If you run your site on WordPress hosting, this setup works the same way and keeps order confirmations and password reset emails out of spam too.
Common Email Authentication Mistakes to Avoid
- Publishing two SPF records after adding a new tool, which can break SPF entirely.
- Exceeding the 10 lookup limit by stacking too many includes.
- Adding the DKIM key but never activating signing in the email platform.
- Jumping straight to p=reject before checking reports, which can block your own invoices or newsletters.
- Using a DMARC reporting address nobody reads, so problems go unnoticed.
- Forgetting subdomains or unused domains. Domains that never send mail should publish an SPF record that allows no senders and a DMARC policy of reject, so scammers cannot use them.
- Assuming authentication fixes everything. It proves identity. It does not fix poor list quality, spammy content or a damaged sender reputation.
When Should You Get Professional Help?
Most small businesses can handle SPF, DKIM and DMARC with the steps above. It is worth bringing in your hosting provider, IT support or an email deliverability specialist when:
- DMARC reports show unknown servers sending large volumes as your domain
- You are near the SPF lookup limit and need record flattening or restructuring
- You run your own mail server on a VPS or dedicated server
- You manage many domains or brands
- Important mail is still landing in spam after all three records pass
Key Takeaways
- SPF, DKIM and DMARC are DNS records that prove your emails genuinely come from your domain.
- SPF lists approved senders, DKIM signs each message, and DMARC checks alignment and sets the policy for failures.
- Since 2024 and 2025, Google, Yahoo and Microsoft require all three for senders of 5,000 or more emails per day.
- Keep one SPF record per domain and stay under 10 DNS lookups.
- Enable DKIM in every platform that sends as you, not just your main mailbox.
- Start DMARC at p=none, read the reports, then move to quarantine and reject.
- WordPress forms should send through SMTP from an address on your own domain.
Frequently Asked Questions
What is the difference between SPF, DKIM and DMARC?
SPF checks whether the sending server is on your approved list. DKIM verifies a digital signature that proves the message came from your domain and was not changed. DMARC confirms the From address aligns with a passing SPF or DKIM check and tells inboxes whether to deliver, quarantine or reject failures.
Do I need all three records?
Yes, for the best inbox placement and protection. SPF and DKIM each verify part of the picture, but neither stops someone from spoofing your visible From address on its own. DMARC connects them and enforces a policy. Major providers now require all three for bulk senders, and smaller senders benefit too.
Can DMARC block my legitimate emails?
It can if you start with a strict policy before every sending service is authenticated. That is why experts recommend beginning with p=none, which only collects reports. Once reports confirm your real mail passes, you can move to p=quarantine and then p=reject without disrupting invoices, newsletters or form notifications.
How long does it take for SPF, DKIM and DMARC to work?
The records usually start working within minutes to a few hours after you publish them, depending on your DNS TTL settings. Full propagation can take up to 48 hours. Improved inbox placement may take longer, because providers also weigh your sending history and reputation.
How do I check if my email authentication is working?
Send a message to a Gmail account, open it, and choose “Show original.” Gmail displays PASS or FAIL for SPF, DKIM and DMARC. Free online checkers such as MXToolbox and Google Admin Toolbox can also inspect the records in your DNS for syntax errors.
Why do my emails still go to spam if SPF and DKIM pass?
Authentication proves who you are, not whether recipients want your mail. Spam complaints, sudden volume spikes, purchased lists, broken links, misleading subject lines and a poor domain or IP reputation can all push mail to spam. Also check that DMARC passes, because SPF and DKIM must align with your From domain.
Do I need SPF and DMARC on a domain that does not send email?
Yes. Unused domains are attractive to scammers because nobody monitors them. Publish an SPF record that authorizes no servers and a DMARC record with a reject policy. This tells inbox providers that any email claiming to come from that domain is fake and should be blocked.
Does my web hosting affect email deliverability?
It can. If your website or mailboxes send email from a shared server, the server’s IP reputation and its DNS setup both matter. A good host lets you edit DNS records easily, supports DKIM signing, and helps you route website email through authenticated SMTP rather than unauthenticated server mail.
Conclusion
Most “my emails go to spam” problems are not mysteries. They come down to three DNS records that tell the world which servers can speak for your business, prove each message is genuine, and decide what happens to imposters.
Set up SPF, enable DKIM for every service that sends as you, and roll out DMARC gradually while you read the reports. Your clients see your emails, and scammers lose the ability to pose as you.
If you are not sure where your DNS lives or how your website’s email is being sent, the team at Web Host Servers is happy to point you in the right direction. Reach out to our support team any time, day or night, and we will help you get your domain’s email on solid footing