Why have only 61% of manufacturers adopted DMARC?
In brief
Only 61% of manufacturers have published a DMARC record, and just 19% enforce p=reject. Learn why DMARC adoption stalls in manufacturing and what to do next.

Only 61% of manufacturers studied have published a DMARC record. The DMARC adoption rate among all 4,796 manufacturer domains measured shows just 19% enforcing p=reject — meaning 81% of manufacturers leave their domain open to spoofing or rely on a monitoring-only policy. Most organizations start at p=none to gather aggregate reports without disrupting mail flow, then stall there. In manufacturing, legacy IT stacks and limited security expertise extend the stall, especially where email is tightly integrated with ERP and supply-chain platforms.
At a glance
Quick takeaways
- 61% of manufacturers studied have a DMARC record published (2,938 of 4,796 domains).
- Only 19% of all manufacturers enforce p=reject; 31% of DMARC publishers do.
- 44% of DMARC publishers use p=none — reporting only, no enforcement.
- Major inbox providers including Google, Yahoo, and Microsoft require DMARC for bulk senders.
- Manufacturing is among the most targeted industries for email-based attacks.
What is DMARC and why does it matter for manufacturers?
DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an email-authentication protocol that tells receiving servers how to handle messages that fail SPF or DKIM checks. By publishing a DMARC record with an enforcement policy, organizations instruct receivers to quarantine or reject mail that fails domain authentication — reducing the exposure of their brand to spoofing. For manufacturers whose supply-chain communications often contain sensitive data, DMARC reduces the risk of malicious actors impersonating vendors or partners. A p=reject policy asks receivers not to deliver unauthenticated messages claiming to be from that domain, though each receiver retains its own final handling decision.
How many top manufacturers actually use DMARC?
According to Palisade’s research of 4,796 global manufacturing domains, 2,938 (61.26%) have a DMARC record published. While this shows progress, it also means nearly two-fifths of manufacturers still lack basic email authentication, leaving them vulnerable to spoofing attacks. For comparison, Palisade’s DMARC adoption benchmark of the NRF Top 100 U.S. retailers found 98 of 100 publishing a valid record, with 86.7% of those publishers enforcing quarantine or reject — a gap that illustrates how adoption lags across less-regulated sectors.
What DMARC policies are manufacturers adopting?
The study broke down policy adoption among the 2,938 DMARC-publishing domains. Percentages are relative to that base; some domains publish multiple DMARC records covering parent and subdomain scopes, so domain counts can exceed the base and percentages need not sum to 100%.
- None (p=none): 1,287 domains (43.8% of DMARC publishers) — reporting only, no enforcement action.
- Quarantine (p=quarantine): 914 domains (31.1% of DMARC publishers) — suspicious mail is directed to the junk folder.
- Reject (p=reject): 902 domains (30.7% of DMARC publishers; 18.8% of all 4,796 manufacturers) — unauthenticated messages are blocked outright.
Why are many manufacturers still using a “none” policy?
Organizations often start with p=none to gather reporting data without disrupting email flow. However, without moving to quarantine or reject, the data never translates into security. In manufacturing, legacy IT stacks and limited security expertise can delay policy upgrades, especially when email systems are tightly integrated with ERP and supply-chain platforms.
How does insufficient DMARC affect email deliverability?
Major inbox providers including Google, Yahoo, and Microsoft require DMARC for bulk senders. Domains without a proper DMARC record risk being flagged as low-trust, causing marketing and transactional emails to land in spam or be rejected entirely. This reduces campaign effectiveness and can impact revenue-critical communications.
What other email-authentication standards should manufacturers implement?
Beyond DMARC, manufacturers should ensure SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) are correctly configured. SPF defines which servers are authorized to send mail on behalf of a domain, while DKIM adds a cryptographic signature to each message. Palisade's SPF checker and DKIM checker can verify published records against the DNS currently seen by resolvers.
Can BIMI improve brand visibility while enhancing security?
Brand Indicators for Message Identification (BIMI) lets organizations display their logo next to authenticated emails, reinforcing brand trust. BIMI requires a fully enforced DMARC policy (p=quarantine or p=reject) before a valid BIMI record will be recognized by supporting mailbox providers. Palisade’s BIMI checker can verify whether a published BIMI record meets the requirements.
What steps should an IT team take to upgrade DMARC policy?
Upgrading from p=none to enforcement is a staged process, not a single DNS edit. The sequence below applies whether the team manages email internally or through a third-party platform:
- Review current DMARC reports to identify every source sending under the domain and confirm which ones produce aligned SPF or DKIM passes.
- Align SPF and DKIM records for all sending services — ERP notifications, marketing platforms, and any other application that sends mail using the domain.
- Move from p=none to p=quarantine once the reports show no legitimate source failing authentication. Monitor deliverability through the transition.
- After confirming quarantine does not affect legitimate mail, advance to p=reject for full enforcement.
- Continue monitoring aggregate reports for new senders or configuration drift after policy changes.
How does digital transformation increase email risk for manufacturers?
Modern manufacturing relies on interconnected IoT devices, cloud-based ERP, and third-party logistics platforms, expanding the attack surface. Each new integration creates additional email endpoints that can be spoofed. Without robust email authentication, attackers can impersonate vendors, inject malicious links, or exfiltrate data through phishing campaigns.
What are the financial implications of poor email security?
Phishing incidents can lead to ransomware, data breaches, and loss of intellectual property, all costly for manufacturers. Additionally, reduced email deliverability hampers sales outreach, marketing ROI, and supplier communications, directly affecting the bottom line. Investing in DMARC, SPF, DKIM, and BIMI can yield a high return by preventing these losses.
How can Palisade help manufacturers achieve full email protection?
Palisade is agentic DMARC software that analyzes aggregate-report data, identifies sending sources and authentication or alignment issues, and creates prioritized remediation tickets. The Email Security Score tool gives a quick health check of published records. Palisade's agent proposes each policy step — including the move from p=quarantine to p=reject — for human review before any change is applied.
Where can I learn more about improving email security in manufacturing?
Start by checking your domain’s published email authentication records with the Email Security Score, then review the results against the step-by-step upgrade path above.
Evidence
Sources and further reading
- Palisade manufacturing DMARC study: 4,796 global manufacturing domains measured, 2025. Data on file; contact Palisade for details.
- Palisade research: NRF Top 100 U.S. retailer DMARC adoption
- Google bulk sender guidelines
- Yahoo sender best practices
- DMARC reports: how to read them
- What is DMARC?
Questions readers ask
Frequently asked questions
What is the difference between p=none, p=quarantine, and p=reject?
p=none requests aggregate reports without changing how receivers treat failing messages. p=quarantine asks receivers to treat failing messages as suspicious and direct them to junk. p=reject asks receivers not to deliver failing messages at all. Receivers make their own final handling decisions under each policy.
Do I need to change my existing email infrastructure to publish DMARC?
No. DMARC works alongside existing SPF and DKIM records — it reads their results against the visible From domain. You add a DNS TXT record at _dmarc.yourdomain.com. Before moving to enforcement, confirm that every legitimate sending service produces an aligned SPF or DKIM pass.
How long does it take to see results after switching to p=reject?
Receivers start applying a newly published or changed DMARC policy once DNS propagates, typically within 24–48 hours. Aggregate reports from participating receivers will reflect the change in the next reporting window (usually 24 hours). Monitor reports and deliverability before and after the change to confirm no legitimate source is affected.
Is BIMI required for DMARC compliance?
No. BIMI is an optional extension that displays a verified logo next to authenticated messages in supporting mailboxes. It requires a fully enforced DMARC policy (p=quarantine or p=reject) but is independent of DMARC compliance itself.

Written by
Samuel ChenardCEO & Co-Founder, Palisade
Samuel Chenard is the CEO and co-founder of Palisade, agentic DMARC software for IT teams and MSPs, from one domain to thousands.
More from Samuel →


