SMB1001 DMARC requirements: SPF, DKIM and DMARC by tier

November 21, 2026

Email spoofing is one of the cheapest ways to attack a small business. A criminal sends an email that looks like it came from your domain, asking a client to pay a "new" bank account or a staff member to buy gift cards. SMB1001 deals with this through one control that gets stricter as you move up the tiers. Here is what it asks for, based on SMB1001:2026.

Silver (Level 2): SPF on every domain

Control 2.12.0.0 requires an SPF record on every domain you use to send email. SPF lists the services that are allowed to send mail for your domain, such as Microsoft 365, Google Workspace, your CRM or your newsletter tool.

The common trap is forgetting a sender. Every time you add a marketing, invoicing or helpdesk tool that sends email as you, the SPF record needs updating.

Gold (Level 3) and above: SPF, DKIM and DMARC with enforcement

Control 2.12.1.0 replaces the Silver control and requires all three, on all domains used to send organisational email:

  • SPF: a valid record listing every authorised sending service.

  • DKIM: signing enabled on all outbound email, using at least 1024-bit keys (2048-bit is better).

  • DMARC: a published policy with a reporting address, set to p=quarantine or p=reject, with alignment to both SPF and DKIM.

The standard also asks you to review these DNS records at least once a year and after any major change to your email systems.

The mistake that fails most Gold assessments

A DMARC record at p=none does not meet the control. p=none only monitors. It tells receiving mail servers to deliver spoofed email anyway. Many businesses set up DMARC years ago at p=none and never moved it, so they believe they are covered when they are not.

Other common gaps:

  • DKIM not turned on, so many legitimate messages fail DMARC alignment.

  • Parked or secondary domains with no DMARC record, which criminals can still spoof.

  • Nobody reading the DMARC reports, so problems are never spotted.

How to reach enforcement without blocking real email

Jumping straight to p=reject can stop invoices, password resets and newsletters from arriving. The safe path is:

  1. Confirm SPF is complete (you should have done this for Silver).

  2. Turn on DKIM in Microsoft 365 or Google Workspace, and in every other tool that sends as your domain.

  3. Publish DMARC at p=none with a reporting address, and read the reports for a few weeks to find every legitimate sender.

  4. Fix any sender that fails, then move to p=quarantine.

  5. Once reports are clean, move to p=reject.

  6. Add a DMARC record at p=reject to any domain that never sends email.

DMARC reports are hard to read raw. A DMARC management service turns them into a list of senders and failures, which is what makes the move to enforcement safe.

Why it is worth doing properly

Enforced DMARC protects your clients and suppliers as much as it protects you, because it stops criminals from sending convincing email in your name. It is also one of the few controls that clients, insurers and supplier risk tools can check from the outside, because anyone can look up your DMARC record.

How CyberGrape helps

CyberGrape runs a managed DMARC service with Suped. We map every legitimate sender, move your domains to enforcement in stages and keep monitoring the reports, so you meet SMB1001 Gold without losing email. Take the free readiness assessment or talk to us about your domains.