Skip to content
Cloutions
Cloutions

SPF, DKIM and DMARC: Keep Your Company Emails Out of Spam

7 min read

SPF, DKIM and DMARC: keep your company emails out of spam

You send a quote to a client and hear nothing back. You call, and it turns out your email was sitting in their spam folder. If this has happened to you more than once, the problem most likely isn't what you write, but how your domain is configured. For Gmail, Outlook and other providers to trust your messages, and for your company emails to stay out of spam, your professional email needs three technical records: SPF, DKIM and DMARC.

The names aren't friendly, but the idea is simple: prove that emails sent under your company's name really come from you and not from an impostor. Here is what each one does and how to tell whether yours are set up properly.

Why your company emails end up in spam

Email was designed decades ago without impersonation in mind. Anyone can send a message that claims to come from "invoices@yourcompany.com" even if they have nothing to do with you. That is why email providers examine every message they receive and decide whether to deliver it to the inbox, send it to spam or reject it.

They look at many things: the reputation of the sending server, the content, whether recipients tend to open your messages or mark them as spam and, increasingly, whether the domain is authenticated. In 2024 Gmail and Yahoo tightened their requirements for bulk senders, and authentication went from a recommendation to a condition. Even if your company doesn't send bulk email, a domain without SPF, DKIM or DMARC starts at a disadvantage.

The most common causes are these:

  • The domain has no authentication records at all because nobody set them up when the email was created.
  • A new tool (a newsletter platform, invoicing software, a CRM) sends emails on the company's behalf and was never added to the configuration.
  • Records exist, but they are badly written or duplicated, and providers ignore them.
  • Someone is using your domain to send spam or fraud attempts, which is damaging its reputation.

What SPF is: the list of authorised servers

SPF (Sender Policy Framework) is a record published in your domain's DNS, a kind of internet directory that also says where your website or your email lives. In that record you write which servers are allowed to send email on behalf of your domain: your email provider (Google Workspace, Microsoft 365 or your hosting server), the platform you use for newsletters, your invoicing software.

When a server receives an email from you, it checks that list. If the message comes from a server on it, all is well. If not, it becomes suspicious.

Common SPF mistakes

  • Having two SPF records. There can only be one per domain. If each provider asked you to "add their SPF" and two separate records were created, the result is an error. They need to be merged into one.
  • Forgetting tools. If your invoicing software sends invoices from your address and isn't included, those invoices stand a good chance of ending up in spam.

What DKIM is: a signature on every message

DKIM (DomainKeys Identified Mail) adds a digital signature to every email you send. Your email provider signs the message with a private key that only it knows, and the matching public key, which allows the signature to be checked, is published in your domain's DNS.

That way, whoever receives the email can verify two things: that the message comes from a server authorised by your domain, and that nobody has altered it along the way. It works like the wax seal on a letter: if it arrives intact, the contents are the original.

DKIM is switched on from your email provider's control panel, which gives you a record to copy into the DNS. Every service that sends in your name (the newsletter tool, the online shop, the CRM) should also have its own signature set up. Many companies skip this step because email "already works" without it, until it stops arriving.

What DMARC is: what to do when something fails

SPF and DKIM run checks, but they don't say what to do when a check fails. That is the job of DMARC (Domain-based Message Authentication, Reporting and Conformance), another DNS record in which you tell other providers how to treat emails that claim to come from your domain but fail the checks. It has three policy levels:

PolicyWhat it meansWhen to use it
p=noneDo nothing special, just send me reports.At the start, to see what is happening without any risk.
p=quarantineIf it fails the check, treat it as suspicious and send it to spam.Once you know all your legitimate emails are authenticated.
p=rejectIf it fails the check, reject it.When you want maximum protection against impersonation.

DMARC has an advantage that is often overlooked: reports. Providers that receive emails using your domain send you regular summaries of which servers are sending them and whether they pass the checks. Thanks to these you can spot tools you forgot to configure and, above all, third parties trying to pass themselves off as your company.

Why you shouldn't start with the strictest policy

If you switch on "reject" without first reviewing all your outgoing email, you could block your own invoices, order notifications or newsletters. The sensible approach is to start with "none", analyse the reports for a while, fix whatever is missing and tighten the policy gradually.

How to check whether your professional email is set up properly

You don't need to be technical to do a first review:

  1. Look at the headers of a sent email. Send a message to a Gmail account and, from that account, open the message menu and choose "Show original". You will see whether SPF, DKIM and DMARC appear as PASS or FAIL.
  2. Use a DNS checker. There are free tools that show the records published for your domain and warn you about syntax errors.
  3. List everything that sends email in your name. Note down everything that sends email from your domain: day-to-day email, the online shop, invoicing software, the CRM, the newsletter platform and your website forms.
  4. Check your website forms. It is common for a website to send contact notifications from the hosting server itself without authentication, and for them to get lost.

Beyond the setup: what else matters

SPF, DKIM and DMARC are the foundation, but on their own they don't guarantee that everything reaches the inbox. Other factors count too:

  • The reputation of the domain and the server. If your email goes out from a server shared with other websites that send spam, you may pay the price.
  • The content. Subject lines in capitals, lots of shortened links or a message that is just an image raise suspicion.
  • Mailing lists. In newsletters, sending to old or purchased addresses drives up complaints and bounces. As well as harming delivery, it can clash with data protection rules.

Email impersonation is only one of the threats facing a company with an online presence. In our article on critical vulnerabilities in web development we go through others worth keeping an eye on.

Who should take care of the setup

The records are changed in the domain's DNS, usually in the control panel of the provider where you registered it or in your hosting panel. It is a short job if you know what to do, but a mistake can leave the whole company without email or break the verification of other services. The sensible option is for whoever manages your domain and email to handle it, and to review it every time you add a tool that sends messages.

That is why it makes sense to include it in a good hosting and maintenance service: email authentication isn't configured once and forgotten, it is monitored along with the rest of the infrastructure.

If your emails end up in spam or you don't know whether your domain has SPF, DKIM and DMARC, at Cloutions we can review it with you and leave it properly configured. Tell us what problem you are having with your email and we will take a look.

Frequently asked questions

Can I set up SPF, DKIM and DMARC if I use a free Gmail or Outlook account?

No. These records are published in the DNS of a domain of your own, so you need professional email on your domain, whether with Google Workspace, Microsoft 365 or your hosting.

Can switching on DMARC stop my emails being delivered?

It can happen if a strict policy is switched on straight away and a service that sends in your name isn't authenticated. That is why you start with a policy that only generates reports and tighten it after reviewing them.

If I have SPF, DKIM and DMARC, will my emails never go to spam again?

There is no total guarantee, because providers also weigh the server's reputation, the content and how recipients react. What is certain is that without authentication your messages are far more likely to end up in spam or be rejected.

More articles

Our office

Where are we

Av. Bon Pastor 15 · 08380 Malgrat de Mar (Barcelona)

Get directionsGoogle Maps map