Email Security
DMARC, SPF and DKIM: Stop Attackers Sending Email as Your Company
If anyone can send email that says it is from your domain, your customers will eventually pay an invoice you never sent.
Business email compromise (BEC) and invoice fraud cost businesses more than almost any other cybercrime, and many cases start with an email that appears to come from a trusted domain. Three DNS records decide whether receiving mail servers can tell a real message from your company from a forged one.
What each record does
| Record | Purpose |
|---|---|
| SPF | Lists which servers are allowed to send mail for your domain |
| DKIM | Adds a cryptographic signature so receivers can verify the message was not altered |
| DMARC | Tells receivers what to do when SPF/DKIM fail (none, quarantine, reject) and sends you reports |
Why it is no longer optional
Since 2024, Google and Yahoo require SPF, DKIM and a DMARC record from bulk senders, and many enterprise customers check DMARC during vendor assessments. A DMARC policy of p=none only monitors; it does not stop spoofing. The goal is p=reject.
Getting to p=reject without breaking mail
- Publish DMARC at p=none with reporting, and read the reports for a few weeks.
- Identify every legitimate sender: your mail platform, CRM, billing, HR and marketing tools.
- Configure SPF and DKIM for each one, staying within SPF's 10-lookup limit.
- Move to p=quarantine, then p=reject once legitimate mail passes.
- Protect look-alike and unused domains too, with a reject policy.
DMARC stops exact-domain spoofing. It does not stop look-alike domains or compromised real mailboxes, so pair it with payment verification processes and mailbox monitoring.
Already hit by invoice fraud?
Our forensic investigators trace business email compromise, preserve evidence and help recover what can be recovered.
See digital forensicsFrequently asked questions
What is DMARC?
DMARC is a DNS record that tells receiving mail servers how to handle messages that fail SPF and DKIM checks for your domain, and sends you reports about who is sending mail as you.
Does DMARC stop all phishing?
No. It stops attackers sending email that uses your exact domain. It does not stop look-alike domains or attacks from compromised legitimate mailboxes.
What DMARC policy should we use?
Start at p=none to monitor, then move to p=quarantine and finally p=reject once all legitimate senders pass authentication.
PITOWINGS Research
OSCP, CEH and ECES certified testers, SOC analysts and certified forensic investigators at PITOWINGS.
Keep reading
All articlesPITOWINGS · Insights
AI Security
11 min read
Agentic AI Security in 2026: Prompt Injection, MCP Servers and the OWASP Agentic Top 10
AI agents now read email, call APIs and change records on their own. The attack surface is no longer the prompt; it is everything the agent can see, call and remember.
PITOWINGS · Insights
Cryptography
10 min read
NIST IR 8547 Is Final: RSA and ECC Deprecated After 2030 — Your Post-Quantum Migration Plan
The quantum deadline now has a date on it. Here is what NIST's final transition plan changes, and a practical migration path that starts with knowing where your cryptography is.
PITOWINGS · Insights
Security Operations
9 min read
AI in the SOC: What AI Agents Can and Cannot Do for Threat Detection in 2026
AI can read every alert. It still cannot decide, on its own, whether to take your payment system offline at 3 a.m.


