SPF, DKIM and DMARC: stop people sending email as your company

29 October 2026 · 2 min read · اقرأ بالعربية

Most invoice fraud in the Gulf does not start with a hacked mailbox. It starts with an email that looks like it came from your finance team — because nothing stops anyone from putting your domain in the "From" line. Three DNS records fix that: SPF, DKIM and DMARC.

Check your domain first with the free SPF & DMARC checker, then read on.

SPF: who is allowed to send

SPF is a TXT record on your domain that lists the servers allowed to send its mail. A typical Microsoft 365 company has:

v=spf1 include:spf.protection.outlook.com -all
  • Add one include: for every service that sends as you — Microsoft 365 or Google Workspace, your CRM, your billing system, your newsletter tool.
  • End with -all (reject others) or ~all (soft fail). Never +all: it allows the whole internet.
  • Keep one SPF record per domain. Two records make both invalid.
  • SPF allows at most 10 DNS lookups. Too many include: entries silently break it.

DKIM: a signature on every message

DKIM signs each outgoing email with a private key; receivers check it with a public key published in your DNS. You switch it on in your mail provider (Microsoft 365 Defender portal, Google Admin → Apps → Gmail → Authenticate email) and add the records they give you. Every other service that sends as you needs its own DKIM key too.

DMARC: what to do when checks fail

SPF and DKIM only describe; DMARC decides. It is a TXT record at _dmarc.yourdomain.com:

v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Roll it out in three steps:

  1. p=none with a rua= reporting address. For two to four weeks, read the reports to find every system that sends as you.
  2. Fix SPF and DKIM for each legitimate sender, then move to p=quarantine — failing mail goes to spam.
  3. When reports are clean, move to p=reject. Spoofed mail is now refused.

A DMARC record stuck at p=none is the most common finding in our scans: it looks like protection, but blocks nothing.

Domains that never send email

Parked and secondary domains are popular for spoofing because nobody watches them. Lock them completely:

v=spf1 -all
_dmarc  →  v=DMARC1; p=reject

Add MTA-STS for inbound mail

MTA-STS tells other mail servers to deliver to you only over a valid TLS connection, so mail to you cannot be silently downgraded to plain text. It needs a small policy file on https://mta-sts.yourdomain.com and one TXT record.

Keep it checked

Mail setups drift: a new marketing tool, a migrated mailbox, an SPF record edited by a vendor. A free Sain Shield account rechecks SPF, DMARC and MTA-STS on every scan, and the full scan also watches for lookalike domains registered to phish your customers.

Check your own domain

Run the free scan to see how your website and email measure up.

Free security scan