Stop email spoofing

Make sure nobody can send convincing email as your domain — the first step in most business email compromise.

The challenge

  • No DMARC policy, or stuck at p=none for years
  • SPF broken by too many DNS lookups
  • DKIM not turned on for every sending service

A practical plan

  1. Scan your domain and fix SPF so every sender is listed within 10 lookups
  2. Turn on DKIM for each service that sends as you
  3. Publish DMARC at p=none, read reports, then move to quarantine and reject
  4. Check look-alike domains, which DMARC cannot stop

Who it is for

Any organization that sends email from its own domain — especially finance, sales and support teams that customers trust.

Outcomes

  • Fakes of your exact domain rejected at major mailbox providers
  • Every legitimate sender authenticated
  • Better inbox placement for your real mail

Checklist

  • One SPF record, 10 lookups or fewer
  • DKIM on for every sender, 2048-bit keys
  • DMARC at p=reject with reporting
  • Unused or parked domains publish v=spf1 -all and p=reject
  • Look-alike domains reviewed quarterly

Step-by-step plan

A realistic timeline for a small team.

Week 1
  • Scan the domain and fix SPF syntax and lookup count
  • List every service that sends as you
Week 2
  • Turn on DKIM for each sender
  • Publish DMARC at p=none with a rua address
Weeks 3–6
  • Read DMARC reports and fix failing senders
  • Move to p=quarantine (start with pct=25 if unsure)
Week 7+
  • Move to p=reject
  • Monitor look-alike domains, which DMARC cannot block

Start with a free check

No account needed.

Questions

Can DMARC stop all phishing?

No. It stops fakes of your exact domain. Look-alike domains and compromised accounts need other controls such as brand monitoring and training.

What about subdomains?

Subdomains inherit the main DMARC policy unless you set sp= or publish their own record.

See where your domain stands

Free for up to 3 domains. No card, no installs.

Start free