Without DMARC, anyone can send email that appears to come from your store — putting your customers and your brand at risk.
DMARC helps protect your domain from being used in fake emails by monitoring senders and supporting stronger enforcement when your legitimate email services are confirmed.
Email remains the primary attack vector for fraud targeting eCommerce businesses and their customers.
Attackers send email appearing to come from your domain, deceiving customers into sharing credentials or payment information.
Fake order confirmations and shipping notifications exploit trust in your brand to redirect customers to fraudulent sites.
Without DMARC, your legitimate transactional email is more likely to be filtered into spam, reducing open rates and revenue.
A spoofing incident using your domain can permanently erode customer trust — even when the attack is not your fault.
Each policy defines how receiving mail servers handle messages that fail DMARC authentication checks.
| Policy | Behavior | Risk | Recommended For |
|---|---|---|---|
| Not set | No DMARC enforcement. Domain can be spoofed freely with no visibility or control. | High | — |
| p=none | Monitor-only mode. Aggregate reports are generated but no action is taken on failing mail. | High | Initial setup and report collection only |
| p=quarantine | Failing messages are routed to the spam or junk folder rather than the inbox. | Medium | Transition phase before full enforcement |
| p=reject | Failing messages are rejected by the receiving server before delivery. Full spoofing protection. | Low | All verified legitimate senders configured |
_dmarc.[domain] TXT record via Cloudflare DNS-over-HTTPS. Only publicly accessible DNS records are checked. No DKIM validation, SPF parsing, or live email delivery testing is performed.