SPF, DKIM and DMARC Explained: Stop Your Business Emails Landing in Spam

← Back to Blog

Three small DNS records quietly decide two things that matter enormously to your business: whether your emails actually reach your customers' inboxes, and whether a criminal can send email that looks like it came from you.

Those records are called SPF, DKIM and DMARC. Most Australian small businesses have never heard of them, have them half-configured by whoever set up their email years ago, or had them switched on in a hurry and broken something in the process. This guide explains what each one does in plain English, how to check yours, and — importantly — the safe order to roll them out so you don't block your own invoices.

Why Email Needed Fixing in the First Place

Email was designed in an era when the internet was a small, trusting place. The underlying protocol lets any mail server claim to be sending on behalf of any domain. There is nothing built in that stops a scammer's server from putting accounts@yourbusiness.com.au in the From field of an email they send to your biggest client.

That design gap is exactly what makes business email compromise and invoice fraud so effective — and why the ACSC consistently lists email-based fraud among the most reported cybercrimes affecting Australian businesses. If you've read our guide on protecting your business from phishing attacks, you'll know how convincing a spoofed email can be.

SPF, DKIM and DMARC are the industry's answer. They're three DNS records — text entries attached to your domain name — that let receiving mail servers verify whether an email claiming to be from you genuinely is. Get them right and two things happen: criminals find it much harder to impersonate your domain, and services like Gmail and Outlook gain confidence that your legitimate email is legitimate, so less of it lands in spam.

SPF: Who Is Allowed to Send Mail for Your Domain

SPF (Sender Policy Framework) is a published list of the servers and services authorised to send email on behalf of your domain. When an email arrives claiming to be from your domain, the receiving server looks up your SPF record and checks whether the sending server is on the list.

Think of it as the guest list at the door. If the sending server isn't on the list, the email fails the SPF check — a strong signal that something is wrong.

The catch is that your “guest list” is almost certainly longer than you think. It's not just Microsoft 365 or Google Workspace. Many SMBs also send email from:

  • Accounting software sending invoices (Xero, MYOB, QuickBooks)
  • Email marketing platforms (Mailchimp, Campaign Monitor)
  • CRMs and booking systems that send on your behalf
  • Your website's contact form or e-commerce order confirmations
  • Scanners, printers and line-of-business applications

Every one of those needs to be represented in your SPF record, which is why there's no universal “correct” SPF value we can give you to paste in — the right record depends entirely on which services send mail for your domain. A record copied from a blog post that misses your invoicing platform will push your own invoices towards spam.

One more trap: a domain must have exactly one SPF record. Two separate SPF records don't add together — they cause the check to fail outright. It's one of the most common misconfigurations we find during assessments.

DKIM: Proving the Email Wasn't Tampered With

DKIM (DomainKeys Identified Mail) works differently. Instead of listing authorised senders, it adds a cryptographic signature to every email you send. Your mail service signs each outgoing message with a private key; the matching public key is published in your DNS. The receiving server uses that public key to verify two things: the message genuinely came from a system authorised by your domain, and it wasn't altered in transit.

If SPF is the guest list, DKIM is a tamper-evident wax seal on the envelope. Broken seal, broken trust.

DKIM has a practical advantage over SPF: it survives forwarding. When someone forwards your email, SPF often fails (because the forwarding server isn't on your list), but a valid DKIM signature usually remains intact. That's one reason modern email authentication leans on both checks together rather than either one alone.

Enabling DKIM is done inside each sending platform — Microsoft 365, Google Workspace, your marketing tool — which generates the keys and tells you what to publish in DNS. Each service that sends for you needs its own DKIM setup; switching it on for Microsoft 365 doesn't cover your newsletter platform.

DMARC: The Policy That Ties It Together

SPF and DKIM do the checking, but on their own they don't tell receiving servers what to do when a message fails. That's DMARC's job.

DMARC (Domain-based Message Authentication, Reporting and Conformance) is a published policy that says: “If an email claims to be from my domain but fails authentication, here's how I want you to treat it.” There are three policy levels:

DMARC PolicyWhat It Tells Receiving ServersWhen It's Appropriate
None (monitor)Deliver the mail as normal, but send me reports about what's passing and failingThe starting point for everyone — gives you visibility with zero delivery risk
QuarantineTreat failing mail with suspicion — typically deliver it to the spam or junk folderOnce reports confirm all your legitimate senders are passing authentication
RejectRefuse failing mail outright — it never reaches the recipient at allThe end goal, after weeks of clean monitoring at quarantine

DMARC also adds something SPF and DKIM lack: reporting. Receiving mail servers send back aggregate reports showing who is sending email claiming to be your domain and whether it passed. This is how businesses discover forgotten sending services — and how they discover that someone overseas is actively spoofing their domain.

The expensive mistake: jumping straight to “reject”. A strict DMARC policy published before every legitimate sender is passing SPF or DKIM doesn't just block criminals — it blocks you. We've seen businesses flip the switch and silently stop their own invoices, booking confirmations and quotes from being delivered, because their accounting platform or website forms weren't authenticating. The failures are invisible from your end: the email leaves your system fine and simply never arrives. Always start at “none”, read the reports, fix what's failing, and tighten gradually.

The Google and Yahoo Requirements: Why This Stopped Being Optional

In early 2024, Google and Yahoo began enforcing new requirements for mail sent to their users. All senders are expected to have properly configured SPF or DKIM, and senders who dispatch large volumes of email to Gmail and Yahoo addresses face stricter rules again — including having both SPF and DKIM configured, publishing a DMARC policy, keeping spam-complaint rates low, and offering one-click unsubscribe on marketing mail. The exact thresholds and details have evolved since the initial announcement, so check the current sender guidelines from Google and Yahoo directly rather than relying on older articles.

The practical takeaway for Australian SMBs is simple: the world's largest mailbox providers now treat email authentication as a baseline expectation, not a nice-to-have. Unauthenticated mail is increasingly filtered or refused — regardless of how legitimate your business is. Microsoft has moved in the same direction with its own sender requirements. The era of “we'll sort out those DNS records someday” is over.

How to Check What You Currently Have

You don't need to be technical to find out where you stand:

  1. Use a free online checker. Tools like MXToolbox or dmarcian let you enter your domain and see your SPF, DKIM and DMARC records instantly, with warnings for common problems like duplicate SPF records or a missing DMARC policy.
  2. Inspect a real email's headers. Send an email from your business account to a personal Gmail address, open it, and choose “Show original”. Gmail displays a plain summary showing whether SPF, DKIM and DMARC each passed or failed.
  3. List everything that sends as your domain. Walk through your software stack — accounting, CRM, marketing, website, booking systems — and note which ones send email using your domain name. This list is the foundation of getting the records right.

Whether you're on Microsoft 365 or Google Workspace, both platforms support all three standards well — but neither configures them completely for you, particularly for third-party senders.

The Safe Rollout Order

The order matters. Here's the sequence we follow when bringing a client's domain up to standard:

  1. Inventory your senders. Everything else depends on knowing every service that sends mail as your domain.
  2. Get SPF right. One record, covering every legitimate sender, within the technical limits SPF imposes on record complexity.
  3. Enable DKIM on every sending service. Start with your main email platform, then work through marketing tools, invoicing software and website mail.
  4. Publish DMARC in monitoring mode. Policy set to “none” with reporting switched on. Nothing changes for your mail flow — you're just gathering intelligence.
  5. Watch the reports for several weeks. Raw DMARC reports are dense XML, so most businesses use a reporting service (free tiers exist) to turn them into readable dashboards. Fix any legitimate sender that's failing.
  6. Tighten to quarantine, then reject. Only once the reports show your legitimate mail consistently passing. Many organisations tighten gradually, applying the stricter policy to a percentage of mail first.

For a typical small business, the full journey from nothing to an enforced policy takes one to three months — most of which is simply monitoring. Rushing the timeline is how invoices go missing.

Want to know whether your domain is protected — or quietly failing authentication checks right now? Our free IT assessment includes a review of your email authentication, backups and security posture, with findings explained in plain English.

Book Your Free Assessment →

Common Mistakes We See in the Wild

  • Two SPF records. Usually left behind after switching email providers or adding a marketing tool. Instead of doubling protection, it breaks SPF entirely.
  • A forgotten sender. The website contact form or the invoicing platform wasn't included, and its mail has been skirting the edge of spam folders for months.
  • DKIM enabled on the main platform only. Your Microsoft 365 mail signs correctly, but your newsletter platform sends unsigned — and gets filtered.
  • DMARC published with no reporting address. The policy exists, but nobody is receiving the reports, so failing senders and active spoofing go unnoticed.
  • “Set and forget”. You adopt a new CRM next year, it starts sending as your domain, nobody updates the records, and deliverability quietly degrades. Email authentication needs an owner, not a one-off project.

That last point is why email authentication belongs inside ongoing IT management rather than a once-off fix — the same reason security awareness training works as a programme rather than a single session. Technical controls and trained staff reinforce each other: DMARC makes it harder to spoof your exact domain, so attackers fall back on lookalike domains — which trained eyes are far more likely to catch.

The Bottom Line

SPF says who may send mail for your domain. DKIM proves the mail wasn't forged or altered. DMARC tells the world what to do when a message fails those checks — and sends you reports so you can see what's happening in your name.

Together, they protect two things every business depends on: your deliverability and your reputation. The major mailbox providers now expect them, criminals exploit their absence, and a careful, staged rollout costs very little compared with a single successful invoice-fraud incident against one of your clients.

If you'd rather not decode DNS records and XML reports yourself, this is exactly the kind of work covered under our managed IT services — set up properly once, then monitored so it stays that way as your software stack changes.

Not Sure If Your Email Domain Is Protected?

We offer a free, no-obligation IT assessment that includes a look at your email authentication setup — so you know exactly where you stand before anything breaks or gets spoofed.