
Email Authentication: Implementing SPF, DKIM and DMARC to Stop Domain Spoofing
| File No. | IGRS-057/2026 |
| Subject | Technical implementation guide for email authentication standards for Indian organizations |
| Category | Threat Intelligence |
| Author | Manuj Kumar Pandey |
| Published | 2026-05-27 |
| Reading time | 12 minutes |
Spoofing your organization's email domain is trivially easy without authentication controls. SPF, DKIM, and DMARC together stop it. Implementation guide for Indian IT teams.
Email Authentication: SPF, DKIM, and DMARC
Email is the most common attack vector, and email spoofing — forging the sender to impersonate trusted entities — underlies phishing and business email compromise. SPF, DKIM, and DMARC are the authentication standards that prevent spoofing and protect both an organisation's domain and its recipients. For Indian organisations, implementing these correctly is a foundational security and brand-protection measure. This guide explains them.
The Email Spoofing Problem
By default, email allows anyone to claim any sender address. Attackers exploit this to send messages appearing to come from trusted domains — a bank, a company, or a colleague. Email authentication closes this gap by letting receiving servers verify that a message genuinely comes from an authorised sender for that domain, rejecting forgeries before they reach inboxes.
The Three Standards
| Standard | Function |
|---|---|
| SPF | Specifies which servers may send for a domain |
| DKIM | Cryptographically signs messages to prove authenticity |
| DMARC | Sets policy and reporting for failures |
SPF: Authorising Senders
Sender Policy Framework (SPF) is a DNS record listing the mail servers authorised to send email for a domain. When a message arrives, the receiving server checks whether it came from an authorised server. SPF prevents attackers from sending spoofed mail through unauthorised servers, though it has limitations — it does not survive forwarding well and only checks the envelope sender.
DKIM: Signing Messages
DomainKeys Identified Mail (DKIM) adds a cryptographic signature to outgoing messages, which receiving servers verify using a public key in DNS. This proves the message genuinely originated from the domain and was not altered in transit. DKIM complements SPF by providing tamper-evidence and surviving forwarding better, strengthening the overall authentication picture.
DMARC: Policy and Enforcement
DMARC ties SPF and DKIM together with a policy telling receivers what to do when authentication fails — monitor, quarantine, or reject. Crucially, DMARC also provides reports showing who is sending mail using the domain, revealing both legitimate sources and spoofing attempts. Moving from a monitoring policy to strict rejection, once legitimate senders are confirmed, decisively blocks domain spoofing.
Implementation Approach
Implementing email authentication follows a careful sequence: publish an SPF record listing authorised senders, configure DKIM signing on mail systems, deploy DMARC initially in monitoring mode to gather reports, identify and authorise all legitimate senders, then progressively tighten the DMARC policy to quarantine and finally reject. Rushing to strict enforcement before confirming legitimate senders risks blocking valid mail, so the staged approach is essential.
Why It Matters for India
For Indian organisations, email authentication protects against the spoofing that powers phishing and BEC fraud — among the most damaging threats. It also protects brand reputation by preventing attackers from impersonating the organisation to its customers. As phishing and BEC continue to cause major losses, properly implemented SPF, DKIM, and DMARC are a foundational defence that every organisation should deploy. The reporting DMARC provides also offers ongoing visibility into who is attempting to abuse the domain, turning email authentication into both a preventive control and an intelligence source.