Business

Email security for small business: SPF, DKIM, DMARC made plain

A Melbourne plumbing business we heard about through a reader email spent three weeks chasing an invoice a customer swore they’d paid. They had. Just not to the plumber. A scammer had registered a domain one character off the real one, copied the branding from a genuine email thread, and sent a “updated bank details” message that looked, to a bookkeeper working through fifty emails before lunch, entirely normal. The money was gone within the hour. This is email security for small business in its most expensive form: not a hypothetical, but a Tuesday afternoon.

The frustrating part is that the fix for a huge chunk of this problem has existed for years and most Australian small businesses have never touched it. Three technical standards, SPF, DKIM and DMARC, exist specifically to stop someone sending email that pretends to be from your domain. They’re free. They don’t require new software. And almost nobody outside IT circles has heard of them, which is exactly why we’re doing this the plain-English way.

What’s actually going wrong

Email was built in the 1980s on a system with essentially no identity checking. Anyone can type any “from” address into an email and hit send, the same way anyone can write any return address on a paper envelope. For decades this didn’t matter much. Then phishing became a business model.

Two different scams exploit this gap. One is domain impersonation, where a scammer buys a look-alike domain (yourbusiness-au.com instead of yourbusiness.com.au) and sends from that. The other, more dangerous version is domain spoofing, where the scammer doesn’t buy anything, they just forge your actual domain in the “from” field, because nothing stops them. A customer’s inbox shows your real email address and your real name. SPF, DKIM and DMARC are the three controls that, together, close that second hole.

Verdict: if your business sends invoices, quotes or payment requests by email, this isn’t optional admin. It’s the digital equivalent of locking the shop.

SPF: the guest list for your domain

SPF stands for Sender Policy Framework. Think of it as a guest list published at your domain’s front door. It’s a small text record, stored in your domain’s DNS settings (DNS is the system that translates a domain name into the technical addresses computers use), that lists exactly which mail servers are allowed to send email claiming to be from you. Your email provider’s servers, maybe a billing platform like Xero, maybe an email marketing tool like Mailchimp.

When another mail server receives a message claiming to be from your domain, it checks that list. Sender’s on it, fine. Sender’s not on it, that’s a red flag the receiving server can act on.

The catch with SPF on its own is that it only checks where the mail came from technically, not what the “from” line actually displays to the human reading it. A scammer can sometimes still get a spoofed-looking email through if SPF is the only control in place. It’s necessary, not sufficient.

Verdict: SPF is the easy first step and almost every hosting provider or email platform has a short setup guide for it. Do this one first.

DKIM: a tamper-proof seal, not a lock

DKIM, DomainKeys Identified Mail, works differently. Rather than checking where a message came from, it attaches a digital signature to each email, generated using a private key your mail server holds, that the receiving server can verify against a matching public key published in your DNS. If anyone alters the email in transit, even slightly, the signature breaks and the receiving server knows something’s off.

It’s closer to a wax seal on an envelope than a guest list. The letter might have been opened by the wrong person, but at least you’ll know if it was tampered with on the way.

Setting up DKIM usually means turning it on inside whatever platform sends your email, Microsoft 365, Google Workspace, or your website’s transactional email service, and then pasting a key into your domain’s DNS. It sounds fiddlier than SPF and in our experience it often is, mostly because businesses run mail through more services than they remember (the CRM, the accounting software, the newsletter tool) and each one needs its own DKIM setup if it’s sending mail on your behalf.

Verdict: worth the extra twenty minutes, particularly if you use more than one platform to send customer-facing email.

DMARC: the part that actually stops the scam

Here’s the bit most small businesses miss entirely, and it’s the one that matters most. SPF and DKIM are checks. DMARC, Domain-based Message Authentication, Reporting and Conformance, is the instruction that tells a receiving mail server what to actually do when those checks fail.

Without a DMARC record, a receiving server might notice that an email failed SPF and DKIM and just… deliver it anyway, perhaps with a vague warning banner, perhaps with nothing at all. With a DMARC record published, you can tell every mail server in the world: if a message claiming to be from our domain fails these checks, quarantine it, or reject it outright.

DMARC also has a reporting function that’s genuinely useful and almost nobody uses. You can ask receiving servers to email you a daily or weekly summary of every message claiming to be from your domain, including ones you never sent. It’s how a lot of businesses first discover they’re being actively spoofed, sometimes for months, because nobody was watching.

Our mildly unpopular opinion here: most of the official guidance on DMARC tells small businesses to start in “monitoring mode” (policy set to none) for weeks before moving to quarantine or reject. That’s sound advice for a large enterprise with a dedicated IT team watching reports daily. For a five-person business, we reckon it’s often better to get SPF and DKIM solid, then move DMARC to quarantine reasonably quickly rather than sitting in monitor-only limbo for a month while nobody actually reads the reports. The risk of sitting unprotected tends to outweigh the risk of a rare legitimate email getting caught, especially once SPF and DKIM are already clean.

Verdict: DMARC is the one that converts “we have security settings” into “scammers can’t easily forge our domain.” Don’t skip it because it looks like the hardest of the three.

Why this matters more for Australian small business right now

Business email compromise, where a scammer either hijacks or convincingly impersonates a legitimate business email account to redirect payments, remains one of the costliest scam categories reported through Scamwatch, the Australian Competition and Consumer Commission’s scam reporting service. The ACCC has repeatedly flagged payment redirection scams targeting businesses as a persistent and expensive problem, and the Australian Signals Directorate’s Cyber Security Centre publishes small business-specific guidance on exactly these email authentication standards.

If your business ever has a serious compromise, a well-documented set of email controls also matters for how you handle disclosure obligations. If customer data ends up exposed as part of a spoofing incident, the Notifiable Data Breaches scheme explained for small business is worth reading before, not after, something goes wrong.

There’s a reputational angle too, one business owners underestimate. Gmail and major providers increasingly treat domains without SPF, DKIM and DMARC as lower trust by default, meaning legitimate marketing emails and invoices from under-configured domains can land in spam even when nothing malicious is happening. Fixing your email authentication isn’t just defence, it’s basic deliverability hygiene.

What this actually takes to set up, realistically

None of this requires buying anything. It requires access to your domain’s DNS settings, which usually sit with whoever registered your domain (a telco, a web host, or a registrar like one of the larger Australian providers) and twenty to ninety minutes depending on how many services send mail on your behalf.

  • Log into your domain’s DNS management panel and check whether an SPF record already exists; many hosting providers set a basic one by default but it’s often incomplete once you add a CRM or invoicing tool.
  • Turn on DKIM signing inside each platform that sends email as your business, then publish the key it gives you into DNS.
  • Publish a DMARC record starting at a sensible policy, point the reporting address at an inbox someone will actually check, and review what comes back after a couple of weeks.

If that list sounds like a foreign language, this is exactly the kind of half-day job worth handing to whoever manages your web hosting or IT support, rather than attempting cold on a Friday afternoon. It’s genuinely a once-and-done task, not an ongoing subscription or maintenance chore, which makes it unusual among cybersecurity advice.

The other half of the job: your team, not just your DNS

SPF, DKIM and DMARC protect your own domain from being forged. They do nothing to stop a scammer registering a convincing look-alike domain and emailing your customers from that instead, which is a separate, harder problem with no single technical fix. The realistic answer there is the boring one: train staff to verify any changed payment details by phone, using a number they already have on file rather than one in the email, and treat urgency as a warning sign rather than a reason to move fast.

The same instinct applies to how to spot a fake parcel delivery text before you click and other everyday scam formats; the pattern of urgency plus a slightly-off detail repeats constantly across phishing, smishing and business email compromise alike.

Password hygiene matters here too. A compromised email account with weak or reused credentials makes every one of these technical controls irrelevant, because the scammer is sending from inside your actual mailbox, not forging it. If you haven’t reviewed how your team manages logins, our rundown of password managers compared for Australians is a reasonable place to start.

Is this worth doing today

Yes, and the reason is almost boringly practical: this is one of the few areas of small business cybersecurity where the fix is free, permanent and doesn’t ask anything of your customers. Compare that to the ongoing vigilance required to spot how quishing scams actually work or to keep staff alert to every new scam format, and SPF, DKIM and DMARC look like unusually good value for the effort involved.

We’d put it on the same shelf as backing up your accounting data or registering your domain renewal a year in advance: not exciting, rarely discussed at the pub, but the kind of unglamorous admin that saves a business from a very bad week. The plumber from the opening would probably agree.

— Dale Whitfield, Founding Editor, Tech Geek

Featured image: AI-generated illustration.

Dale Whitfield

Dale Whitfield is the Founding Editor of Tech Geek. He set the brief the site still runs on — clear, useful technology journalism with no hype — and writes its bigger news analysis pieces. Dale has spent years following how technology companies behave and translating their announcements into what they actually mean for readers.

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Back to top button