Do You Need SPF DKIM and DMARC for Business Email?

Ammar Sohail 4 min read
Do You Need SPF DKIM and DMARC for Business Email?
In this post
  1. What do SPF, DKIM and DMARC actually do?
  2. Do small businesses really need SPF DKIM and DMARC?
  3. How do you set up SPF for your domain?
  4. How do you turn on DKIM?
  5. What should your first DMARC record say?
  6. Who should have access to your DNS?

If you send email from your own domain, yes, you need SPF, DKIM and DMARC set up. Google's sender rules ask every sender to authenticate with SPF or DKIM, and anyone sending more than 5,000 messages a day to Gmail accounts needs all three. Without them, your quotes and invoices are more likely to land in spam.

Each one is a short DNS record. None of this needs code, but you do need access to wherever your domain's DNS is managed.

What do SPF, DKIM and DMARC actually do?

Think of them as three checks a receiving mail server runs on your message.

  • SPF is a list of the servers allowed to send mail for your domain.
  • DKIM adds a digital signature to each message, so the receiver can tell it wasn't altered on the way.
  • DMARC tells receivers what to do when a message fails those checks, and sends you reports about it.

Google's help page explains that DMARC only passes when the message authenticates with SPF, DKIM or both, and the domain in the From address lines up with the domain that passed. That last part trips up a lot of small businesses using newsletter tools.

Do small businesses really need SPF DKIM and DMARC?

For a business sending a few dozen emails a day, Google's formal DMARC rule for bulk senders doesn't apply to you. The baseline does, though: SPF or DKIM for everyone. In practice we'd set up all three, because the work takes under an hour and it stops other people from spoofing your domain in phishing emails.

It matters more if you use a newsletter or CRM tool. Those services send mail on your behalf, and unless you authorise them, Gmail sees a stranger using your name. If you're planning campaigns, read this alongside our email marketing service page.

Google also expects bulk senders to keep their spam rate below 0.30% in Postmaster Tools. Good authentication won't fix a list full of people who didn't ask for your emails, but it removes the avoidable problems.

How do you set up SPF for your domain?

SPF is a TXT record on your main domain. It looks roughly like this: v=spf1 include:_spf.google.com ~all. That example allows Google Workspace to send for you. Your provider will give you the exact "include" value to use.

Two rules catch people out. A domain can have only one SPF record, so if you add a second tool, merge it into the existing line rather than creating another. And SPF allows a maximum of 10 DNS lookups, so a long chain of "include" entries can break it.

How do you turn on DKIM?

DKIM is switched on inside your email provider, not your DNS panel. In Google Workspace it's under Apps, Google Workspace, Gmail, Authenticate email. The tool generates a key, you paste it into your DNS as a TXT record (some providers use CNAME records instead), then go back and click start authentication.

Do this once for every service that sends mail as you: your mailbox provider, your newsletter tool, your invoicing software, and the contact form on your website. Each has its own DKIM setting.

What should your first DMARC record say?

Add a TXT record at _dmarc.yourdomain.com. A safe starting value is v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. The "p=none" policy blocks nothing. It just collects reports so you can see which services send mail as you.

After a few weeks, once the reports show only legitimate senders passing, you can move to "quarantine" and later "reject". Going straight to reject on day one is how businesses end up blocking their own invoices.

Finally, test it. Send a message from your domain to a Gmail address, open it, choose "Show original" and look for PASS next to SPF, DKIM and DMARC. Google's full requirements are on its email sender guidelines page, and the rules can change, so check there before relying on any summary, ours included.

Who should have access to your DNS?

You need to, or at least someone you trust does. If your agency registered the domain in its own account, you may be waiting on them for every change. We wrote about this in who should own your domain name.

Your next step is simple. Log in to your DNS provider today, look for existing TXT records, and write down every service that sends email for you. If you'd rather have it done properly, get in touch and we'll check your records as part of a website development or hosting move.

Common questions

How long do DNS changes for email records take?

Often a few minutes, but it can take up to 48 hours to spread everywhere. Wait before testing, and don't keep changing records in the meantime.

Will these records stop all spam from my domain being faked?

Not on their own. DMARC set to quarantine or reject is what tells receivers to act on spoofed mail. With p=none you only get reports.

Do I need them if I only use Gmail or Outlook?

Yes, your domain still needs the records. Your provider gives you the values, and you add them wherever your domain's DNS is managed.

You might also like