We're hiring Hiring a systems technician and a sales pro. Join the team We're hiring: tech & sales See roles ↗
Infrastructure & Cloud

SPF, DKIM and DMARC: why your emails end up in spam

Published on November 17, 2026 · 6 min read · by ADMNetwork

You send an important quote and the client never gets it. Days later it turns up in their spam folder, or it does not turn up at all. If this has happened more than once, the problem is probably not what you write but your domain: it is missing three technical records that are now essential for email providers to trust you. They are called SPF, DKIM and DMARC, and in this article we explain what each one does, without the jargon, and why they are no longer optional.

Why your emails end up in spam

Every time you send an email, the receiving server asks a simple question: does this message really come from who it says? Email was designed decades ago with no way of checking that, which is why anyone can put your address in the sender field of a fake message. To defend themselves, Gmail, Outlook and the other providers check whether your domain publishes the credentials that prove the message is legitimate. If they cannot find them, or they are wrong, your email loses points and ends up in spam or rejected.

This has tightened a lot. Since 2024 Google and Yahoo require these records from high volume senders, Microsoft has followed the same path with Outlook.com, and in practice filters increasingly penalise any domain without them, even if it sends little.

SPF: the list of who can send on your behalf

SPF is a record in your domain's DNS that states which servers are authorised to send email with your address. For example: Microsoft 365, your newsletter tool and your invoicing software. When a message arrives, the recipient checks that list to see whether the sending server is on it.

The most common mistake is forgetting a service. The company sets up SPF for its email, but then the invoicing software or the website sends notifications from another server that is not on the list, and those messages land in spam. Another frequent mistake is having two SPF records at the same time, which invalidates both.

DKIM: the signature that proves nobody has tampered with the message

DKIM adds a digital signature to every email that leaves your domain. The receiving server checks it against a public key that you publish in DNS. If the signature matches, it knows two things: the message comes from an authorised server, and nobody has changed it along the way.

Platforms such as Microsoft 365 or Google Workspace sign with DKIM, but in many cases it has to be switched on and the keys published in the domain. It is a step that often gets skipped, because email works the same without it… until it stops arriving.

DMARC: the rule that says what to do with fake emails

DMARC ties the two previous pieces together and adds a policy: it tells the world what to do with an email that uses your domain but fails the checks. There are three levels. With "none" you only observe, without blocking anything. With "quarantine" suspicious emails go to spam. With "reject" they are refused outright.

DMARC also has an advantage few people use: reports. Providers send you summaries of who is sending email with your domain, which helps you discover legitimate services you had not accounted for and, above all, spoofing attempts. It is one of the best defences against phishing that uses your name to deceive your own clients.

How to tell if your domain is set up correctly

There are free online tools that analyse a domain's records in seconds, but reading the results is not always easy. Some signs that something is wrong: clients who say they do not get your emails, replies that take days, "this sender has not been verified" warnings in Gmail, or finding out that someone has sent fake invoices in your name. If your company uses several services that send email, there is probably a gap somewhere.

How to set it up without breaking anything

Order matters. First, take stock of everything that sends email with your domain. Then adjust SPF to include it all, enable DKIM on every service that supports it and publish DMARC in monitoring mode. With a few weeks of reports, fix whatever is missing and only then tighten the policy to "quarantine" and later to "reject". Skipping steps and setting "reject" on day one is the quickest way to make your own invoices stop arriving.

How we do it at ADMNetwork

We review the whole domain, list every service that sends on your behalf and leave SPF, DKIM and DMARC configured and monitored as part of our infrastructure and cloud service. If you are still on a free account, the first step is a different one: we explain it in why your business should not use free Gmail or Hotmail.

Frequently asked questions

Do I need SPF, DKIM and DMARC if my company sends few emails?

Yes. The strictest requirements from Google, Yahoo and Microsoft apply to high volume senders, but spam filters take these records into account in every case. Without them, any company is more likely to see its emails land in spam and to have its domain spoofed.

Can setting up DMARC stop my emails from arriving?

Only if it is rushed. If it is published straight away with a reject policy, without first checking which services send on your behalf, the ones that are not set up properly will stop delivering. That is why you start in monitoring mode and tighten the policy gradually.

How long does it take to set up SPF, DKIM and DMARC?

The initial setup takes a few hours if you have access to the domain's DNS. What takes longer is the DMARC monitoring phase, usually a few weeks, to make sure every legitimate sender is covered before blocking the fake ones.