Anyone Can Send an Invoice From Your Domain. Three DNS Records Decide Whether It Lands.

Laptop screen showing an error

 

Email was built on trust

The protocol that carries email, SMTP, dates back to the early 1980s, when the internet was a small network of universities and research labs. It was designed to deliver messages, not to check who sent them. The “From” address on an email is, by default, whatever the sender chooses to type.

That design decision is why invoice fraud works. A criminal does not need to hack your mailbox to send your client a message that appears to come from your accounts department. Unless your domain is set up to prove which mail is genuine, the receiving server has very little to go on.

The three records that do the proving

Three DNS records, published on your domain, close most of that gap. They are not software and they cost nothing to publish. They simply need to be set up correctly.

  • SPF (Sender Policy Framework) lists the servers that are allowed to send email for your domain: your Microsoft 365 tenant, your accounting package, your newsletter platform. Mail from anywhere else fails the check.
  • DKIM (DomainKeys Identified Mail) adds a digital signature to every outgoing message. The receiving server checks the signature against a public key on your domain, which proves the message came from you and was not altered on the way.
  • DMARC (Domain-based Message Authentication, Reporting and Conformance) tells receiving servers what to do when a message fails those checks: deliver it anyway, send it to junk or reject it outright. It also sends you reports on who is sending mail in your name.

Without DMARC, SPF and DKIM are advisory. With DMARC set to enforce, a forged message using your exact domain gets stopped before it reaches your client.

The big mailbox providers have stopped being patient

In February 2024, Google and Yahoo began requiring bulk senders, those sending more than 5,000 messages a day to their users, to have SPF, DKIM and DMARC in place. Microsoft followed for its consumer Outlook services from 5 May 2025, and non-compliant high-volume mail is now rejected rather than filtered.

Most South African SMEs never send 5,000 emails a day, so these rules do not apply to them directly. The direction of travel matters more. The same checks feed into how every message is scored, and a domain with no authentication increasingly looks like a domain that should not be trusted. That is one common reason legitimate quotes and invoices end up in a client’s junk folder.

Where most businesses actually stand

Many business domains have an SPF record that was set up years ago and never updated, so newer services sending on the company’s behalf fail it. DKIM is often not switched on at all. DMARC, where it exists, is frequently left at p=none, which collects reports but tells receivers to deliver failing mail anyway.

A DMARC record set to p=none is a starting point, not protection. The proper path is:

  1. Publish DMARC at p=none and read the reports for a few weeks to find every legitimate service sending as you.
  2. Fix SPF and enable DKIM for each of those services.
  3. Move to p=quarantine, so failing mail goes to junk.
  4. Move to p=reject, so forged mail is refused outright.

Skipping straight to reject without the reporting stage is how businesses accidentally block their own invoices. Doing it in order avoids that.

What these records do not stop

Authentication protects your exact domain. It does not stop a criminal registering a lookalike domain, a swapped letter or a different ending, and sending from that. Staff and clients still need a simple rule for payment changes: any request to change banking details is confirmed by phone, on a number already on file, before money moves.

Check your domain before someone else uses it

Setting up SPF, DKIM and DMARC properly is a short, well-defined piece of work with a lasting payoff: fewer genuine emails lost to spam, and far fewer opportunities for someone to invoice your clients in your name. Enyuka manages business domains and DNS and configures authentication for Microsoft 365 tenants. Ask us to check where your domain stands.