What is DMARC, and does my small business need it?
DMARC stops scammers sending email that looks like it's from you. What it is, whether you need it, and how to set it up safely, in plain English.
Published · updated
// short answer
DMARC is a DNS record that tells mail providers what to do with email that claims to be from your domain but fails SPF and DKIM checks. If your business has its own domain, you need it, even if you rarely send email.
Most small businesses never think about email security until something odd happens. A customer forwards an invoice you never sent. A supplier asks why you changed your bank details. Someone replies to an email that looks like it came from you, but didn't.
DMARC is the setting that helps stop that. It sounds technical, but the idea is simple, and turning it on is usually a short job. This guide explains what it is, whether you need it, and how to set it up without breaking your own email.
The problem DMARC solves
Email was designed decades ago, when nobody expected strangers to lie about who they were. By default, anyone can send a message that claims to be from accounts@yourbusiness.co.za. The "From" line is just text. There is no built-in check.
That's what email spoofing is: sending mail that pretends to come from your domain. It's the starting point for a lot of phishing, because people trust a familiar name. A fake invoice from you is far more convincing than one from a stranger.
Three DNS records work together to fix this:
- SPF lists the servers that are allowed to send email for your domain.
- DKIM adds a digital signature to each message, so the receiver can tell it wasn't altered and really came from an approved sender.
- DMARC ties the two together. It tells receiving mail servers what to do when a message claims to be from you but fails those checks, and it asks them to send you reports about it.
Without DMARC, a receiving server sees a failed SPF or DKIM check and has to guess what you want. With DMARC, you tell it.
What a DMARC record looks like
DMARC is a single TXT record in your domain's DNS, published at a special name: _dmarc.yourbusiness.co.za. A typical starting record looks like this:
v=DMARC1; p=none; rua=mailto:dmarc@yourbusiness.co.za
Here's what each part means:
v=DMARC1says "this is a DMARC record". It must come first.p=is the policy: what receivers should do with mail that fails the checks.rua=is where receivers should send daily summary reports.
There are three policies:
p=nonemeans "watch only". Nothing is blocked. You just get reports.p=quarantinemeans "treat failures as suspicious", which usually sends them to spam.p=rejectmeans "refuse failures outright". This is the strongest protection.
Does my small business need it?
If your business has its own domain name, the honest answer is yes, even if you don't send much email.
- If you send email from your domain, DMARC protects your customers and suppliers from fakes that use your name. It also helps your genuine mail land in inboxes, because major mailbox providers increasingly expect bulk senders to have SPF, DKIM and DMARC in place.
- If you never send email from your domain, you still need it. A domain with no email is an easy target for spoofing, because nothing contradicts the fake. For these domains, a strict "we send nothing" setup is quick and safe.
For a domain that never sends mail, the usual records are:
yourbusiness.co.za TXT "v=spf1 -all"
_dmarc.yourbusiness.co.za TXT "v=DMARC1; p=reject;"
The first says no server is allowed to send for this domain. The second tells receivers to reject anything that claims otherwise.
How to set it up without breaking your email
The main risk with DMARC is moving too fast. If you jump straight to p=reject before every legitimate sender is set up properly, some of your own mail could be blocked. Think of your newsletter tool, your accounting software that emails invoices, or your website's contact form.
A safe path looks like this:
- Check SPF and DKIM first. Make sure your main email provider (Google Workspace, Microsoft 365, your host) is in your SPF record and is signing mail with DKIM. Most providers have a setup page for this.
- Publish DMARC with
p=noneand a report address. Use a mailbox you actually read, or a free DMARC report service that turns the reports into something readable. - Read the reports for two to four weeks. They show every server sending mail as you. Look for legitimate senders that are failing, such as a booking system or a marketing tool, and add them to SPF or set up DKIM for them.
- Move to
p=quarantine. Once your own mail passes, tighten the policy. You can usepct=to apply it to a percentage of mail first, for examplepct=25. - Move to
p=reject. When quarantine has run quietly for a while, switch to reject. This is the setting that actually stops spoofed mail.
// free, passive, 30 seconds
Check your DMARC record in seconds
Common mistakes
- Two SPF records. A domain must have only one SPF record. If you add a second instead of editing the first, SPF breaks for everyone.
- A typo in the DMARC name. The record must live at
_dmarc(with the underscore), not on the main domain. - Reports going nowhere. If the
ruaaddress doesn't exist, you lose the information that tells you it's safe to tighten the policy. - Stopping at
p=none. Many domains publish a DMARC record once and never come back to it. The protection only starts at quarantine or reject. - Forgetting subdomains. By default the policy also covers subdomains, unless you set a separate
sp=value. That's usually what you want.
How to check yours
You can see your DMARC and SPF records with our free DMARC checker or SPF checker. They're passive: they only read the public DNS records that every mail server on the internet already reads. Nothing is sent to your inbox and nothing is tested against your mail server.
If you'd like the full picture, the website security check covers DMARC alongside your HTTPS certificate, security headers and more. For a wider view of email and website basics, see our website security checklist for small businesses.
When to get help
DMARC is one of those jobs that's simple once it's done, but fiddly the first time, especially if you have several tools sending email for you. If the reports look like a wall of numbers, or you're not sure who has access to your DNS, that's normal.
Odesstra can read the reports with you, find the senders that need fixing, and move your policy to reject safely. Fixes are quoted per job, and nothing starts until you say yes. See website security fixes for how that works, or talk to a human if you'd like to ask a quick question first.