7 min read · Updated 19 Nov 2026
Email spoofing at India's unicorns: 2026 DMARC report
In short: We read the public DMARC, SPF and MTA-STS records of 105 Indian unicorns. Only 31 block fake email outright and 19 still deliver it. The numbers by sector, who does it right, and how to fix your own domain.
Free tool: Email security check (SPF, DKIM, DMARC) →
Every company domain can publish a small DNS record called DMARC. It answers one question for Gmail, Outlook and every other mailbox provider: if an email claims to come from this company but fails authentication, what should happen to it? There are three answers. p=reject blocks it. p=quarantine sends it to spam. p=none delivers it anyway and only reports on it.
On 19 November 2026 we read those public records for 105 Indian unicorns. We sent no email and tested nothing beyond what any mail server reads when a message arrives.
The headline numbers
- 31 of 105 (30%) block fake email outright: p=reject applied to all mail.
- 46 (44%) send it to spam with p=quarantine. That keeps most phishing out of the inbox, but the message still reaches the recipient's mailbox.
- 19 (18%) deliver fake email anyway: 17 publish p=none and 2 have no DMARC record at all.
- 9 more enforce a policy on only part of their mail (pct below 100), so the rest is delivered normally. One applies its policy to just 1% of failing mail.
- 5 enforce DMARC on the main domain but set sp=none, which leaves every subdomain open to spoofing.
- Only 12 (11%) publish MTA-STS, which forces mail sent to them to be encrypted in transit.
Put together, 28 of India's 105 unicorns (27%) let at least some spoofed email from their own domain reach people's inboxes. These companies have millions of customers and send payment, refund and password-reset emails every day, which is exactly the mail fraudsters copy.
By sector
| Sector | Companies | Enforcing on all mail | Not fully protected |
|---|---|---|---|
| Fintech | 24 | 20 | 4 |
| SaaS | 16 | 12 | 4 |
| Consumer | 9 | 7 | 2 |
| E-commerce | 8 | 6 | 2 |
| Edtech | 7 | 5 | 2 |
| B2B | 6 | 3 | 3 |
| D2C brands | 5 | 2 | 3 |
| Logistics | 5 | 3 | 2 |
| Mobility and auto | 7 | 4 | 3 |
| Insurtech | 4 | 3 | 1 |
| Other (gaming, health, crypto, AI, travel, adtech) | 14 | 12 | 2 |
Fintech leads, which fits: banks and payment networks push their partners towards enforcement. D2C brands, B2B marketplaces and auto platforms trail, even though their customers get order, delivery and payment emails every day.
Who gets it right
These 20 companies earned our top grade: p=reject on all mail plus at least one extra layer (a strict SPF record ending in -all, sp=reject for subdomains, or MTA-STS). Their security teams deserve the credit.
- Fintech: Paytm, PhonePe, Zeta, Yubi, Clear (ClearTax), CoinSwitch
- Insurtech: Acko, Policybazaar
- SaaS and developer tools: Zoho, BrowserStack, Icertis, MindTickle, Whatfix, Hasura
- Consumer, edtech and B2B: Zomato, Unacademy, Eruditus, Udaan
- AI and Web3: Fractal, Polygon
We aren't naming the companies that are behind. Records change, and a public list would help fraudsters more than customers. We have written privately, with their own result, to those we could reach.
The four gaps we saw most
- Stuck on p=none. Most teams add DMARC in monitor mode, meaning to move to reject later, and never do because they aren't sure which of their tools (CRM, invoicing, HR, marketing) would break.
- A pct below 100. A partial rollout is a sensible step, but several companies stay at 25% or 50% for a long time, so most spoofed mail is still delivered.
- sp=none for subdomains. To a customer, pay.example.com and support.example.com look just as trustworthy as the main domain.
- No reports. 12 of the records ask for no aggregate reports (no rua= address), so nobody at the company can see who is sending as them.
How to get to p=reject without blocking your own mail
- Publish p=none with a rua= address so reports start arriving.
- Read two to four weeks of reports and list every service that sends as your domain.
- Fix SPF and DKIM for each legitimate sender, and retire the ones nobody owns.
- Move to p=quarantine with pct=25, then 50, then 100, checking the reports at each step.
- Move to p=reject, add sp=reject, and keep reading reports so new tools don't break.
DMARCLens does steps 2 to 5 for you: it reads your DMARC reports, names every service sending as your domain, and tells you exactly what to change before each policy step.
Method
- Public DNS only, read through Cloudflare's DNS-over-HTTPS resolver on 19 November 2026: the _dmarc TXT record, the domain's SPF record and the _mta-sts record.
- One main email domain per company. Subsidiaries and other brands can be set up differently.
- Grades: A = reject on all mail plus an extra layer; A- = reject on all mail; B = quarantine on all mail; C = an enforcing policy on part of the mail; D = p=none; F = no DMARC record.
- If your company is listed and your record has changed, or we used the wrong domain, email deepanshu.saini@duvaxa.com and we'll correct it within a day.
Want your own grade? Our free email security check reads the same records for any domain in under a minute, with no sign-up.
FAQ
Questions
What is email spoofing?
Sending an email with a forged From address so it looks like it came from a company you trust. DMARC is the standard that tells mailbox providers to block those emails.
Is p=quarantine good enough?
It's much better than p=none, because spoofed mail goes to spam. p=reject is better still: the message is never delivered.
Will p=reject block our own emails?
Only if a service that sends as you isn't set up with SPF or DKIM. That's why you read DMARC reports first and move in steps.
How long does it take to reach p=reject?
For most companies four to eight weeks, mostly spent finding and fixing the tools that send as the domain.
How do I check my own domain?
Run our free email security check. It grades DMARC, SPF and MTA-STS and shows what to fix.