Adding a DMARC record to Cloudflare protects your domain from email spoofing and improves deliverability. Follow these simple steps to configure the TXT record in the Cloudflare DNS dashboard.
_dmarc
host.p=none
to monitor email traffic before enforcing policies.DMARC (Domain-based Message Authentication, Reporting & Conformance) tells receiving mail servers how to handle unauthenticated emails. Adding it in Cloudflare prevents spoofed messages from your domain, boosts inbox placement, and gives you visibility through aggregate reports.
Use Palisade’s DMARC Record Generator – simply enter your domain, select a policy (none, quarantine, reject), and copy the generated TXT string.
Choose TXT as the record type. The host name must be _dmarc
and the value is the full DMARC string you generated.
Log into Cloudflare, select your domain, go to the DNS tab, click Add record, then fill in Type = TXT, Name = _dmarc, and paste the DMARC string into the Content field.
If a DMARC record already exists, edit it instead of creating a duplicate. Having multiple DMARC TXT records can cause validation failures.
p=none
policy mean?p=none
tells receivers to monitor email traffic without rejecting or quarantining messages. It’s the safest starting point to collect reports and fine‑tune your SPF/DKIM alignment.
p=none
to p=quarantine
or p=reject
?After a few weeks of monitoring, review the aggregate reports in Palisade’s dashboard. When you’re confident legitimate sources are authenticated, update the p
tag to quarantine
or reject
to enforce stricter handling.
rua
and ruf
tags?rua
specifies an email address for aggregate reports, while ruf
requests forensic (failure) reports. Palisade can forward both to your inbox or a SIEM for analysis.
Use Palisade’s DMARC lookup tool or run a DNS query like dig TXT _dmarc.example.com
. The response should match the string you entered.
Yes. Create a separate TXT record for _dmarc.subdomain.example.com
. This lets you enforce different policies per sub‑domain if needed.
List all legitimate sending sources in your SPF record and ensure each service signs outgoing mail with DKIM. DMARC will then align both SPF and DKIM to pass authentication.
With p=none
, there is no impact on delivery. Only after you switch to quarantine
or reject
will unauthenticated messages be blocked or sent to spam.
SPF is a separate mechanism, but DMARC relies on SPF alignment. Ensure your SPF includes all authorized sending IPs; you can generate one with Palisade’s SPF tool.
DKIM adds a cryptographic signature to each email. DMARC checks that the DKIM signature aligns with the From domain. Use Palisade’s DKIM validator to confirm proper setup.
BIMI (Brand Indicators for Message Identification) displays your logo in supporting inboxes, increasing brand trust. It requires a DMARC policy of p=quarantine
or p=reject
. Learn more at Palisade’s BIMI guide.
Check the aggregate reports weekly during the monitoring phase, then monthly once you’re in enforcement mode. Palisade’s dashboard can send you automated summaries.
Yes. Use a subdomain for testing, apply the DMARC record there, and send test messages. Once verified, copy the record to the primary domain.
For personalized assistance, reach out to Palisade’s support team or explore our suite of email security tools.