Reducing email impersonation with SPF and DMARC
Inventory email senders, configure SPF and DKIM, then move DMARC towards enforcement while testing legitimate messages and understanding its limits.

Your business domain may send more than staff email. Invoices, website forms, newsletters and support tools can all use it. Protecting that domain starts with knowing which services send legitimate mail.
SPF, DKIM and DMARC help receiving systems assess messages claiming to come from your domain. Configure them together and test them before requesting stricter treatment of messages that fail.
Understand what each check covers
SPF uses a DNS record to list the systems allowed to send for the envelope sender domain used in mail delivery. That domain can differ from the From address a person sees. SPF alone doesn’t authenticate the visible sender.
DKIM adds a cryptographic signature associated with a signing domain. It lets the receiver verify the signed parts of a message. A valid signature says nothing about whether the contents or a requested payment can be trusted.
DMARC checks whether successful SPF or DKIM authentication aligns with the visible From domain. An aligned pass from either can satisfy DMARC; both aren’t required. The domain publishes a policy for failing messages and can request reports.
Inventory senders before changing DNS
List your main email platform and every other service sending as the business. Ask finance, marketing and operations about their tools. Include subdomains and domains that no longer send mail.
For each sender, record the domain it uses, who administers it and which authentication settings its supplier supports. Obtain current instructions from that supplier. Don’t paste a generic DNS record over existing settings.
Keep a copy of the current configuration and agree who can make and reverse changes. Domain control, DNS control and email administration may be held in different accounts.
Configure legitimate senders and collect evidence
Have your administrator review the domain’s SPF policy and lookup limits. Publishing multiple separate SPF records for the same domain can create errors; adding every supplier without checking limits can do the same.
Enable DKIM for each sending service and custom domain that supports it. Test messages from each source and inspect the authentication results at the recipient. A record can exist in DNS while invoices or website notifications still fail to use it correctly.
Have aggregate DMARC reports sent to a mailbox the business controls. Review which senders fail and investigate whether they’re legitimate, misconfigured or sending without your permission. Some services send infrequently, so include renewal notices, monthly campaigns and other occasional workflows in testing.
Move towards enforcement in stages
A monitoring policy, p=none, is useful during assessment but doesn’t request rejection of failing mail. Quarantine requests suspicious treatment; reject requests refusal. Receiving systems make their own handling decisions.
After fixing legitimate senders, plan stronger enforcement with a way to monitor delivery and reverse a damaging change. Test forwards and mailing lists as well as direct messages; they can affect authentication results.
Don’t leave monitoring without an owner or a next review date. Equally, don’t move to rejection simply because a checker shows three green ticks. Base the change on representative messages and the report findings.
Keep impersonation limits visible
These controls don’t prevent someone using a different lookalike domain or putting your company name above an unrelated address. They also don’t stop a fraudster sending from a legitimate account they’ve compromised.
Continue verifying payment-detail changes through a known contact. Staff should report suspicious requests even when the message passed authentication. MFA, account reviews and incident-response processes protect different parts of the problem.
Maintain the configuration as services change
Make email-authentication testing part of launching a CRM, changing a newsletter service or replacing a website form. Remove obsolete senders when their services end.
Keep the sender inventory, DNS changes and test results with your domain records. Give someone responsibility for reviewing reports and investigating new senders, so enforcement continues to match the business’s email.


