# Ensure DMARC record exists with enforcement policy (p=reject or p=quarantine)

- Source: https://support.icompaas.com/support/solutions/articles/a_1790787218560381-ensure-dmarc-record-exists-with-enforcement-policy-preject-or-pquarantine
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Cloudflare](https://support.icompaas.com/support/solutions/c_1790786902273285) › [Checks](https://support.icompaas.com/support/solutions/folders/f_1790786912003423)
- Last updated: 2026-09-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure the domain has a DMARC TXT record named \_dmarc, starting with v=DMARC1, with an enforcement policy of p=quarantine or p=reject. This tells receiving servers what to do with mail that fails SPF and DKIM checks.

**Rationale**

SPF and DKIM only check mail; DMARC tells receivers how to act on the result. With p=none, spoofed messages are still delivered. An enforcement policy makes receivers quarantine or reject messages that fail the checks, which greatly reduces phishing that impersonates your domain.

**Impact**

-   Spoofed mail is sent to spam or rejected
    
-   Reports show who is sending mail for your domain
    
-   Legitimate mail that fails SPF or DKIM will also be quarantined or rejected
    

**Default Value**

By default, no DMARC record exists.

**Pre-Requisites**

-   Cloudflare account with Administrator or DNS permissions for the zone
    
-   SPF and DKIM already set up and passing for legitimate mail
    

**Test Plan**

1.  Sign in to the Cloudflare dashboard at [https://dash.cloudflare.com](https://dash.cloudflare.com/).
    
2.  Select your account and the domain (zone) you want to review.
    
3.  Go to DNS > Records.
    
4.  Filter by Type TXT and find the record named \_dmarc.
    
5.  Verify that it starts with v=DMARC1 and contains p=quarantine or p=reject.
    
6.  If there is no DMARC record or it uses p=none, follow the implementation steps.
    

**Implementation Steps**

1.  Sign in to the Cloudflare dashboard at [https://dash.cloudflare.com](https://dash.cloudflare.com/).
    
2.  Select your account and the domain (zone) you want to review.
    
3.  Go to DNS > Records.
    
4.  Select Add record (or Edit the existing record) with Type TXT and Name \_dmarc.
    
5.  Enter the Content, for example: v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@<your-domain>
    
6.  Select Save.
    
7.  After confirming that legitimate mail passes, you can change p=quarantine to p=reject.
    

**Backout Plan**

1.  Sign in to the Cloudflare dashboard at [https://dash.cloudflare.com](https://dash.cloudflare.com/).
    
2.  Select your account and the domain (zone) you want to review.
    
3.  Go to DNS > Records.
    
4.  Select Edit on the \_dmarc record, change the policy back to its previous value (for example, p=none), and select Save.
    

**Reference**

-   [https://developers.cloudflare.com/dns/manage-dns-records/how-to/email-records/](https://developers.cloudflare.com/dns/manage-dns-records/how-to/email-records/)
    
-   [https://developers.cloudflare.com/dmarc-management/](https://developers.cloudflare.com/dmarc-management/)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.