Developer · Validator
DMARC record validator.
Paste a DMARC TXT record and check each tag against RFC 7489, with a plain-language reading of what it asks receivers to do. Runs in your browser; nothing is sent anywhere and no DNS lookup is made.
Input
Result
Paste a record and press Validate.
The DMARC tags this tool checks
v (required): must be exactly DMARC1 and must be the first tag. If it is missing or different, receivers ignore the whole record.
p (required for a policy record): none, quarantine or reject, and it must come second. It applies to the domain and, unless sp is set, to its subdomains.
sp: the same three values, for subdomains only. If absent, p applies to subdomains.
rua and ruf: comma-separated report addresses as URIs, for example mailto:dmarc@example.com. A URI may end with ! and a size limit such as !10m (k, m, g or t; powers of two). Receivers must support mailto:. Without ruf, no failure reports are requested.
adkim and aspf: r (relaxed, the default) or s (strict) alignment for DKIM and SPF.
pct: a whole number from 0 to 100 (default 100), the share of mail the policy is requested for.
ri: seconds between aggregate reports, a 32-bit unsigned integer (default 86400, one day).
fo: colon-separated 0, 1, d, s (default 0); ignored without ruf. rf: report format, only afrf is defined.
Whitespace around = and ; is allowed. Unknown tags are ignored by receivers, so this tool lists them as a note rather than an error.
Worked example
Check v=DMARC1; p=quarantine; pct=50; rua=mailto:dmarc@example.com!10m; adkim=s. It is valid. The tool reads it as: p=quarantine: Failing mail should be treated as suspicious (for example, placed in the spam folder). sp not set: subdomains follow the p policy (quarantine). adkim=s: strict DKIM identifier alignment. pct=50: the policy is requested for 50% of failing mail (a slow-rollout setting; RFC 7489 s6.3 says pct does not apply to the DMARC reports themselves). rua: aggregate reports go to mailto:dmarc@example.com. The !10m on the report address is a 10 MB size limit, and tags you left out take their defaults (aspf=r, ri=86400, fo=0).
Now check p=none; v=DMARC1, the same two tags in the wrong order. It fails with 2 errors: "The first tag must be v=DMARC1. Without it a receiver ignores the whole record." and "The p tag must come second, straight after v=DMARC1 (RFC 7489 s6.3)."
Sources
RFC 7489, Domain-based Message Authentication, Reporting, and Conformance (DMARC): section 6.3 (general record format) and section 6.4 (formal definition) define every tag above. Links last checked 2026-10-26.
Common mix-ups
-
Often assumedIf SPF or DKIM passes, the message passes DMARC.
What the source saysRFC 9989 section 4.4 says DMARC validates the Author Domain by requiring that it share an Organizational Domain with an Authenticated Identifier (relaxed alignment) or be identical to it (strict alignment). A pass for an unrelated domain does not count. [1]
-
Often assumedThe DMARC TXT record belongs at the root of the domain, next to SPF.
What the source saysRFC 9989 stores DMARC Policy Records at a name starting with the label _dmarc. For example.com the record is a TXT record at _dmarc.example.com, and receivers query that name. [1]
-
Often assumedpct=25 applies my p=quarantine policy to a quarter of failing mail.
What the source saysRFC 9989 Appendix A.6 records that the pct tag was removed because it was usually not applied accurately unless set to 0 or 100. It adds a t tag (y or n) in its place, so a receiver following that RFC will not sample by percentage. [1]
Checked against these sources on .
Frequently asked questions
What is a minimal valid DMARC record?
v=DMARC1; p=none is the shortest record that follows the format. Most people add a rua=mailto: address so they receive aggregate reports.
Why does the p tag have to be second?
RFC 7489 section 6.3 says the v and p tags must be present and appear in that order in a policy record. Other tags may follow in any order.
Does this generate a record?
No. Use the example as a starting point and edit it. The tool only checks what you paste.
Does a valid result mean my DMARC is working?
No. It only means the text follows the RFC 7489 format. This tool cannot look up DNS, so it cannot tell whether the record is published at _dmarc.yourdomain, or whether SPF and DKIM align.
Syntax check only
This tool checks record format against RFC 7489 only. It does not query DNS, does not verify report addresses accept reports, and cannot confirm how any mail receiver will act on the record.