02 / Email & domain security

SPF, DKIM and DMARC: what your business should verify

A practical buying and implementation framework for business email authentication, sender inventory and domain impersonation protection.

Evidence-led guideSources checked 16 November 2026

The decision in brief

Email authentication protects the reputation of your domain only when all legitimate senders and the real operating environment are understood. Publishing three records by copying a tutorial is not the same as protecting business email.

What matters most

  • Identify all sending systems before changing records.
  • SPF or DKIM alone is not the same as aligned, enforceable DMARC.
  • Account MFA and payment verification remain necessary.

Understand what each control actually does

SPF helps receiving systems evaluate whether a sender is authorised for a domain. DKIM uses cryptographic signatures to associate a message with a signing domain. DMARC asks receivers to evaluate alignment with the visible From domain and provides reporting and policy instructions.

Google’s sender guidance distinguishes rules for all senders from its additional requirements for senders exceeding 5,000 messages per day to personal Gmail addresses. Those Gmail rules should not be misrepresented as universal law or every mail provider’s policy.

  • SPF: keep a managed list of real outbound services.
  • DKIM: verify signing is active for each supported service.
  • DMARC: understand alignment, reporting and staged enforcement.

Audit before enforcing

Ask your mail administrator to list Microsoft 365 or Google Workspace, bulk email platforms, accounting software, website forms, CRM integrations and outsourced providers that send mail using the company domain. Compare that inventory with DNS and sample authenticated messages.

A monitoring-first approach can reveal legitimate senders before an aggressive DMARC policy interrupts delivery. A deployment partner should explain reporting, exceptions, alignment and the process for changing policy safely.

  • Who has permission to change DNS and mail configuration?
  • What mail would fail if we tightened policy today?
  • Who monitors authentication failures and spoofing reports?

What a product can and cannot solve

DMARC monitoring services may make reports easier to interpret. Email gateways may filter malicious content or impersonation attempts. Neither replaces MFA, staff verification of unusual requests, or mailbox incident response.

A credible vendor assessment should cover what is included, data retention, configuration responsibilities, administrative access, support and recurring price. It should also explain when the business can manage the requirement with existing tools.

Important distinction: Never paste generic DNS records into production or promise that authentication stops all phishing.

Questions to ask before buying

Use these as a written evaluation checklist rather than accepting the first sales proposal.

  1. Which services send mail from our domain?
  2. What enforcement policy is safe today, and how will we measure impact?
  3. Which controls are already included with our email provider?
  4. How will staff verify unexpected payment changes?

Evidence and sources

These links identify the origin of the supporting standards, government advice and vendor descriptions. Source links are not endorsements. Time-sensitive features and commercial terms require fresh verification.

  1. Google: Email sender guidelines · Checked 2026-11-16
  2. FTC: Cybersecurity for Small Business · Checked 2026-11-16
  3. South African Cybersecurity Hub: Cybersecurity Basics · Checked 2026-11-16
Editorial note. This is independent buying guidance, not a hands-on product test, legal assessment, security audit, vendor endorsement or guarantee. No affiliate links appear in this guide.