Loading page
About this tool
Generate a valid RFC 7489 DMARC TXT record with policy, subdomain policy, alignment modes, percentage and reporting addresses.
This generator builds the DMARC TXT record defined by RFC 7489 — the v=DMARC1 policy string published at _dmarc.yourdomain — with every tag validated: policy (p), subdomain policy (sp), sampling percentage (pct 0-100), aggregate and forensic report addresses (rua/ruf), SPF and DKIM alignment modes (aspf/adkim) and failure options (fo). It is for domain owners and email admins rolling out DMARC enforcement or fixing a record their mail provider flagged as invalid.
Open DMARC Record Generator on AltFTool — it loads instantly in your browser.
Provide your input — an image, text, or data.
Let the tool analyze or generate the result.
Review, refine, and reuse the output wherever you need it.
pct bounds, report address syntax, alignment values and policy names are checked against RFC 7489 before output.
Flags risky combinations like p=reject with no reporting address or pct used with p=none.
Warns when reports go to another domain, which requires the RFC 7489 external destination verification record.
A DMARC record is a TXT record published at the name _dmarc.yourdomain.com that starts with v=DMARC1 and tells receiving mail servers what to do with messages that fail SPF and DKIM alignment. It is defined by RFC 7489 and requires SPF and/or DKIM to already be in place.
p=none asks receivers to deliver failing mail normally and only send you reports; p=quarantine asks them to treat failures as suspicious, typically filing them to spam; p=reject asks them to refuse the message outright. The standard rollout path is none, then quarantine, then reject as reports confirm legitimate mail is aligned.
pct is the percentage of failing messages, from 0 to 100, that the quarantine or reject policy is applied to — the rest are treated one level softer. The default is 100, and pct has no effect under p=none since there is no enforcement to sample.
Yes, but RFC 7489 section 7.1 requires the receiving domain to authorize it by publishing a verification TXT record at yourdomain._report._dmarc.reportingdomain.com. Without that record, many receivers will refuse to send reports to the external address.