Cyber Security · Guide

SPF, DKIM & DMARC Explained

If your invoices land in junk, or someone could send email pretending to be you, the fix usually starts with three DNS records. Here is what they do and how to get them right.

The short version

  • SPF says which servers may send for your domain, DKIM signs each message, and DMARC tells receivers what to do when checks fail.
  • Google, Yahoo and Microsoft now expect authenticated mail from bulk senders, so missing records hurt deliverability for everyone.
  • Start DMARC on monitor mode, fix every legitimate sender, then move to quarantine and reject.

If your invoices keep landing in customers' junk folders, or you have ever had a customer ask about an odd-looking email "from you", the cause is very often the same: your domain is not properly set up to prove which emails are genuinely yours.

Three DNS records, SPF, DKIM and DMARC, do that job. Together they help your email get delivered and stop criminals sending email that pretends to be from your business. This guide explains what each one does in plain English, the mistakes we see most often, and the habits that keep your email out of spam.

Why email authentication matters now

Email was designed decades ago without any way to check who really sent a message. Anyone can put your address in the "from" line. Authentication records fix that by publishing, in your domain's DNS, the rules a receiving mail server can check against.

The big mailbox providers have also become much stricter. Google, Yahoo and Microsoft now expect senders, especially anyone sending in volume, to have authentication in place, and mail that fails is increasingly filtered or rejected. Even if you only send a handful of emails a day, being set up properly makes your mail more trustworthy to every receiver.

SPF: who is allowed to send

SPF (Sender Policy Framework) is a list of the servers and services allowed to send email for your domain. A receiving server checks whether the message came from one of them.

For a business on Microsoft 365, the starting point is Microsoft's own servers. But most businesses send from more places than they realise: a CRM, an invoicing or accounting system, a website contact form, an email marketing platform, a recruitment system. Every one of them needs to be accounted for.

Common SPF mistakes
Having more than one SPF record on the same domain (only one is allowed, so both fail), exceeding the limit of ten DNS lookups as more services are added, and forgetting a third-party system that sends as your domain.

DKIM: proving the message was not changed

DKIM (DomainKeys Identified Mail) adds a digital signature to every email you send. The receiving server uses a public key published in your DNS to check the signature, which proves the message really came from a system you authorised and was not altered on the way.

In Microsoft 365, DKIM is switched on per domain in the Defender portal, and it is often left off for custom domains. Third-party senders such as your CRM usually offer their own DKIM records to add too. DKIM is particularly valuable because, unlike SPF, it survives email forwarding.

DMARC: what to do when checks fail

DMARC (Domain-based Message Authentication, Reporting and Conformance) ties SPF and DKIM together. It tells receiving servers what to do with a message that claims to be from your domain but fails the checks, and it asks them to send you reports about what they see.

A DMARC policy has three levels:

  • p=none: take no action, just report. This is where everyone should start.
  • p=quarantine: send failing messages to junk.
  • p=reject: refuse failing messages outright. This is what actually stops criminals spoofing your domain.

The reports are the valuable part early on. They show every service sending as your domain, including the ones you forgot about, so you can fix them before you tighten the policy.

Want to know where your domain stands right now?

Get a free Domain Risk Report

A safe order to set it all up

  1. List every system that sends email as your domain. Ask each team: sales, finance, HR, marketing and whoever manages the website.
  2. Publish one correct SPF record that includes Microsoft 365 and each legitimate third-party sender.
  3. Turn on DKIM for Microsoft 365 and for every third-party sender that supports it.
  4. Publish DMARC at p=none with reporting switched on, and review the reports for a few weeks.
  5. Fix anything failing, then move to p=quarantine and finally p=reject.
  6. Protect domains you do not send from. Parked or old domains should have records saying they send no email at all, so they cannot be used for spoofing either.

Habits that keep you out of spam

Authentication gets you through the door. What you send, and who to, decides whether you stay welcome.

  • Only email people who expect to hear from you. Bought lists and cold bulk sends damage your reputation quickly.
  • Keep lists clean. Remove addresses that bounce and people who have not engaged in a long time.
  • Make unsubscribing easy for anything that is marketing. A one-click unsubscribe is now expected by the big providers.
  • Send marketing from a dedicated platform, ideally on a subdomain such as news.yourcompany.co.uk, so a campaign issue never affects your everyday business email.
  • Write like a person. Clear subject lines, a real sender name, and no shouting in capitals or strings of exclamation marks.
  • Watch your numbers. A rise in bounces or spam complaints is an early warning. Act on it before it becomes a deliverability problem.

The bottom line

SPF, DKIM and DMARC are not glamorous, but they are among the highest-value hours you can spend on your email. They improve deliverability, they protect your customers from emails pretending to be you, and they are increasingly expected by the companies that decide what reaches the inbox.

If you would like it checked or done for you, it is part of our Microsoft 365 tenant hardening work and our ongoing Microsoft 365 management.

Tye Clark
Written by

Tye Clark

Director, On IT

Tye leads On IT with a focus on helping businesses use technology to improve efficiency, security, and growth. Combining technical expertise with a strong commercial mindset, he works closely with clients to ensure technology delivers real business value.

Meet the team

Rather We Handled It?

Everything in this guide is something we do for clients every week. These are the services that cover it.

Common Questions

What DMARC policy should we use?

Start with p=none and reporting switched on so you can see who sends email as your domain. Once every legitimate sender passes SPF or DKIM, move to p=quarantine and then p=reject, which is what actually stops spoofing.

Why do our emails go to junk even with SPF set up?

SPF alone is rarely enough. Receivers look at DKIM, DMARC alignment, your sending reputation and the content itself. A common culprit is a third-party system, such as a CRM or invoicing tool, sending as your domain without being included in your records.

Keep Reading

All articles

Stop Your Emails Landing In Junk

We'll check your SPF, DKIM and DMARC records, find the senders that are failing, and fix them without breaking the mail you rely on.

Talk to Us

Book a call or send an enquiry.