The short answer: SPF lists the servers allowed to send email for your domain, DKIM adds a digital signature to every message, and DMARC tells receiving mail servers what to do when a message fails those checks and sends you reports about it. Together they stop criminals from sending email that looks like it comes from your company. Since February 2024, Gmail has required all three from anyone sending more than 5,000 messages a day to personal Gmail accounts.
Key takeaways
- SPF lists who may send for your domain, DKIM signs each message, DMARC enforces both on the visible From address.
- Without them, anyone can send email that looks like it came from your company.
- Roll out DMARC in stages: none, then quarantine, then reject, over about 12 weeks.
- Gmail has required all three from senders of 5,000+ messages a day since February 2024.
A familiar fraud in Indian businesses goes like this. A customer receives an email that looks like it is from your accounts team, with your logo and your domain name, saying your bank details have changed. They pay the next invoice into the fraudster’s account. Nobody hacked your mailbox. The criminal simply sent an email with your address in the “From” field, which basic email allows anyone to do.
SPF, DKIM and DMARC are three DNS records that close that gap. They cost nothing beyond setup time, yet many company domains still have them missing or set up wrongly.
What happens when an email claiming to be from you arrives
- Email arrivesFrom: accounts@yourcompany.com
- SPF checkWas it sent from an allowed server?
- DKIM checkIs the signature valid and unchanged?
- DMARC checkDoes the passing domain match the From domain?
- Your policy decidesDeliver, send to spam, or reject
SPF: who is allowed to send
Sender Policy Framework is a TXT record in your domain’s DNS that lists the mail servers permitted to send email for your domain. A domain that uses Microsoft 365 and a marketing tool might publish something like:
v=spf1 include:spf.protection.outlook.com include:mailer.example.net -all
Three common mistakes:
- Forgetting a sender. Your CRM, billing software, website contact form and HR system may all send mail as your domain. List every one, or their mail will fail.
- Too many lookups. SPF allows a maximum of 10 DNS lookups. Each “include” can use several, and going over the limit makes SPF fail for everything.
- More than one SPF record. A domain must have exactly one. Merge them into a single record.
DKIM: a signature that proves the message is genuine
DomainKeys Identified Mail adds a cryptographic signature to each outgoing message. The receiving server checks it against a public key published in your DNS. If the signature matches, the message really came from an authorised system and was not altered on the way.
You turn DKIM on in each sending service, such as Microsoft 365, Google Workspace or your email marketing platform, and publish the DNS records it gives you. Use a 2048-bit key where the service supports it.
DMARC: the policy and the reports
DMARC ties the other two to the address people actually see in the “From” line. A message passes DMARC only if it passes SPF or DKIM and the domain that passed matches the visible From domain. This is called alignment, and it is what stops a fraudster passing SPF with their own domain while showing yours.
A DMARC record is a TXT record at _dmarc.yourdomain.com, for example:
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
The policy, p=, has three levels:
- none: deliver as usual, but send reports. Use this first to see who is sending as you.
- quarantine: send failing messages to spam.
- reject: refuse failing messages outright. This is the level that actually protects your customers.
A safe 4-step rollout
DMARC rollout timeline
- Week 1Inventory sendersEvery system that sends as your domain
- Weeks 1 to 2Publish p=noneSPF, DKIM and DMARC with reports
- Weeks 2 to 6Read reportsFix forgotten senders, spot spoofing
- Weeks 6 to 12Quarantine, then rejectReal protection for customers
Step 1: inventory every sender (week 1)
List every system that sends email as your domain: Microsoft 365 or Google Workspace, website forms, CRM, ERP, billing, payroll, ticketing and bulk mail tools. Ask each department; marketing and HR often use services IT does not know about.
Step 2: publish SPF, DKIM and DMARC at p=none (weeks 1 to 2)
Set up SPF and DKIM for each sender, then publish DMARC with p=none and a reporting address.
Step 3: read the reports and fix gaps (weeks 2 to 6)
DMARC reports are XML files that are hard to read by hand, so use a DMARC reporting tool. You will usually find a forgotten sender or two, and you will also see fraudsters already trying to use your domain.
Step 4: move to quarantine, then reject (weeks 6 to 12)
When legitimate mail is passing consistently, move to p=quarantine, watch for a couple of weeks, then move to p=reject. You can use the pct tag to apply the policy to a percentage of mail at first.
What Gmail and Yahoo now require
Since 1 February 2024, Google has required every sender to Gmail to set up SPF or DKIM, keep spam complaint rates below 0.3% and use TLS. Senders of more than 5,000 messages a day to personal Gmail accounts must set up SPF, DKIM and DMARC, with the From domain aligned, and must offer one-click unsubscribe on marketing mail. Yahoo introduced similar rules at the same time. If your newsletters or invoices have started landing in spam, missing authentication is the first thing to check.
Records alone are not enough
DMARC stops criminals using your exact domain. It does not stop look-alike domains, such as an extra letter or a different ending, and it does not stop an attacker who has stolen a real mailbox password. Add multi-factor authentication on email, an email security filter, and a simple rule that bank detail changes are always confirmed by a phone call to a known number. Email remains the most common way attacks start: in Sophos’s 2026 India survey, malicious email and phishing together started more than half of ransomware attacks. See our ransomware protection guide.
How Enterprise Solutions can help
Enterprise Solutions is a corporate solutions provider based in Noida, working with businesses across Delhi NCR and India. If this article raised questions about your own setup, these are the teams to talk to:
- Cloud Infrastructure: Cloud infrastructure services built on Microsoft Azure, from virtual desktops and AI to migration and managed cloud operations.
- Cybersecurity: Security services for endpoint protection, data protection, security monitoring, and vulnerability testing.
Send us an enquiry or call +91 97185 59908 and our team will get back to you.
Frequently asked questions
What is the difference between SPF, DKIM and DMARC?
SPF lists the servers allowed to send email for your domain. DKIM adds a digital signature that proves a message is genuine and unchanged. DMARC checks that SPF or DKIM passed for the domain shown in the From line, tells receivers what to do with failures, and sends you reports.
Which DMARC policy should I start with?
Start with p=none so mail is delivered as usual while you collect reports. When all legitimate senders pass, move to p=quarantine and then to p=reject.
Is DMARC mandatory?
There is no general legal requirement in India, but since February 2024 Gmail requires DMARC from anyone sending more than 5,000 messages a day to personal Gmail accounts, and Yahoo has similar rules.
Why are my emails failing SPF?
Common causes are a sending service missing from the SPF record, more than 10 DNS lookups in the record, or two separate SPF records on the same domain.
Does DMARC stop all phishing?
No. It stops criminals sending mail as your exact domain, but not look-alike domains or attacks from a genuinely compromised mailbox. Use it with MFA, email filtering and payment verification checks.
Keep reading
Sources
- Google Workspace Admin Help: Email sender guidelines
- RFC 7208: Sender Policy Framework (SPF)
- RFC 7489: Domain-based Message Authentication, Reporting and Conformance (DMARC)
- Sophos, The State of Ransomware in India 2026 (PDF)
This article is general information, not legal or regulatory advice. Rules and figures are as published on the date shown, and may change. Please confirm your organisation’s obligations with a qualified professional.
