SPF, DKIM and DMARC Explained for Indian Businesses
Do your quotation and invoice emails land in spam? These three small DNS records are the first thing to check. Here is what each one does, in plain words.
SPF says which servers may send email for your domain. DKIM adds a signature that proves the message was not changed. DMARC tells Gmail, Yahoo and Outlook what to do when those checks fail, and sends you reports. Set up all three and your emails are far less likely to land in spam, and it becomes hard for anyone to pretend to be you.
Why your emails go to spam in the first place
Imagine a stranger sends an email that says it is from your company. How does Gmail know it is not really you? It looks for proof. If it finds none, it treats the email with suspicion.
That proof is SPF, DKIM and DMARC. They are three small records that you add to your domain’s DNS settings. Without them, your quotation, invoice or order email can end up in spam, and anyone can send fake emails in your name.
It also matters more than it did a few years ago. Since 2024, Google and Yahoo ask bulk senders to use SPF, DKIM and a DMARC policy. Google talks about 5,000 or more messages a day to Gmail addresses. Microsoft has brought in similar rules for Outlook.com. Even if you send far fewer emails, a missing record can still push your mail into spam.
You do not need to be one. All three records help every business, big or small.
SPF: who is allowed to send for your domain
SPF stands for Sender Policy Framework. It is a list, kept in your DNS, of the servers and services that may send email as your domain. When an email arrives, the receiving server checks whether the sending server is on your list.
Example SPF record for Google Workspacev=spf1 include:_spf.google.com ~all People break two rules most often:
- One SPF record only. If your domain has two SPF records, SPF fails with an error.
- Ten lookups at most. Every
includecounts towards a limit of 10 DNS lookups. Go over it and SPF fails.
If you send email from more than one place (for example Google Workspace for office mail, a CRM, and a newsletter tool), all of them go into that one record.
DKIM: a signature that proves the email is real
DKIM stands for DomainKeys Identified Mail. Your email system signs every outgoing email with a private key. The matching public key sits in your DNS. The receiver uses it to check the signature. If someone changes the email on the way, the check fails.
You turn DKIM on inside your email platform (Google Workspace, Zoho Mail, Microsoft 365 or your newsletter tool). The platform gives you a record to paste into DNS. Each platform has its own record, so a business with three senders has three DKIM records.
Example DKIM record (shortened)selector._domainkey.yourdomain.in TXT v=DKIM1; k=rsa; p=MIIBIjANBgkq... DMARC: what to do when the checks fail
DMARC sits on top of SPF and DKIM. It tells receivers two things. First, what to do with mail that fails the checks: nothing, send it to spam, or refuse it. Second, where to send you reports about who is sending mail as your domain.
Example DMARC record, added as a TXT record at _dmarc.yourdomain.inv=DMARC1; p=none; rua=mailto:dmarc@yourdomain.in | Policy | What it does | When to use it |
|---|---|---|
p=none | Monitors only. Nothing is blocked. You get reports. | Always start here. |
p=quarantine | Mail that fails goes to spam. | After the reports look clean. |
p=reject | Mail that fails is refused. | The strongest protection. Use it when all your real senders pass. |
Start with p=none. Read the reports for a few weeks, fix every real sender, and only then move to quarantine and reject. Going to reject on day one can block your own invoices.
One more word you will meet is alignment. DMARC passes only when the domain that passed SPF or DKIM matches the domain in the From address your customer sees. That is why SPF can say “pass” and DMARC can still fail.
How the three work together
| Record | The question it answers | Where you set it |
|---|---|---|
| SPF | Is this server allowed to send for this domain? | One TXT record on your domain |
| DKIM | Was this email changed on the way, and does it really come from this domain? | One TXT record for each sending platform |
| DMARC | What should we do if SPF and DKIM do not match the From address, and who should hear about it? | One TXT record at _dmarc |
How to check your records in two minutes
- Send a test email to GmailSend an email from your business address to a personal Gmail account.
- Open “Show original”In Gmail, open the message, click the three dots, and choose Show original.
- Read the top boxYou will see SPF, DKIM and DMARC, each with PASS or FAIL. All three should say PASS.
If any of them says FAIL, SOFTFAIL or NONE, that record is missing or wrong. You can also look up your domain’s TXT records with any free DNS lookup tool. Check that there is exactly one record that starts with v=spf1.
Want us to set this up for you?
We find every system that sends email for your domain, fix SPF, turn on DKIM, and roll out DMARC in stages, so nothing real gets blocked. Then we test it and show you the results.
Set them up in the right order
- List every senderWrite down everything that sends email as your domain: office mail, website forms, your CRM, accounting or invoicing software, your newsletter tool, your help desk.
- Fix SPFAdd one SPF record that includes all of them, and stay under 10 lookups.
- Turn on DKIMSwitch on DKIM in each platform and add the key it gives you.
- Add DMARC with p=noneAdd the DMARC record with
p=noneand a mailbox that receives the reports. - Read the reportsAfter a few weeks you will see everyone who sends mail as you. Fix every real sender that fails.
- Tighten the policyMove to
p=quarantine, then top=reject, when everything real passes.
Mistakes we see again and again
- Two SPF records. Merge them into one.
- A forgotten sender. The contact form on your website, or the billing tool, often sends from a different server.
- Reject on day one. Always start with
p=none. - The record in the wrong place. DMARC lives at
_dmarc.yourdomain.in, not on the main domain name. - A new sender added later. You change your CRM or newsletter tool and forget to update SPF and DKIM.
Using Zoho Mail, Google Workspace or Microsoft 365?
Most Indian businesses use one of these three. Each one shows you the exact SPF value and DKIM record inside its own admin console. Use the values the platform gives you, and do not copy records from random websites. Zoho explains its SPF setup in its help guide, and Microsoft explains DMARC for Microsoft 365.
You add the records in the DNS panel of the place your domain’s name servers point to. That can be your domain registrar, your hosting company, or Cloudflare.
When it is time to ask for help
If you have many senders, a long SPF record, or you are afraid of blocking real mail, it is worth getting help. A wrong record can hide your emails for days before anyone notices. We find every sender, fix the records, test them, and roll out DMARC in safe stages. You can read how it works on our SPF, DKIM and DMARC setup page.
Frequently asked questions
Do I need SPF, DKIM and DMARC if I send only a few emails?
Yes. Google says every sender should have SPF or DKIM, and bulk senders need all three. The records also make it much harder for someone else to send fake emails in your company’s name.
Will DMARC block my own emails?
Not with p=none, because that only monitors. Problems start when you move to quarantine or reject before all your real senders are set up. That is why you should go in stages.
What is the difference between SPF and DKIM?
SPF checks the server that sent the email. DKIM checks a signature on the message itself. You need both, because forwarding can break SPF while the DKIM signature usually survives.
How long before my emails stop going to spam?
Authentication is one part of the story. Your sender reputation, your content and the quality of your list matter too. After the records are correct, many senders see better results within days or a few weeks, but nobody can promise a date.
Where do I add these records?
In the DNS panel of the company that manages your domain’s name servers. That may be your registrar, your hosting company or Cloudflare. If you are not sure, ask whoever manages your domain.
Want us to set this up for you?
We find every system that sends email for your domain, fix SPF, turn on DKIM, and roll out DMARC in stages, so nothing real gets blocked. Then we test it and show you the results.