DMARC Record Generator
Set your DMARC policy, reporting addresses, alignment options, and failure reporting to generate a ready-to-publish DMARC TXT record. Everything runs in your browser.
Domain
_dmarc.example.com. Policy
Reporting
Alignment
Other
| Type | TXT |
| Name | _dmarc |
| Value |
Recommended rollout
- 1 p=none — Start here. Collect aggregate reports for 1-2 weeks to understand who is sending on behalf of your domain.
- 2 p=quarantine, pct=10 — Begin enforcing on a small percentage. Monitor reports for false positives and gradually increase pct toward 100.
- 3 p=reject, pct=100 — Full enforcement. Illegitimate senders are blocked at the mail server. Only move here once all legitimate mail streams pass DKIM and SPF.
About this tool
DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an email authentication protocol that lets domain owners publish a policy telling receiving mail servers how to handle messages that fail DKIM or SPF checks. It is defined in RFC 7489.
How DMARC builds on SPF and DKIM
SPF checks that the sending mail server is authorized to send for the domain. DKIM adds a cryptographic signature that lets the receiving server verify the message was not tampered with in transit. Both operate at the envelope level, though, and neither tells receiving servers what to do when a check fails. DMARC adds that missing enforcement layer and introduces the concept of alignment: the authenticated domain must match the domain in the visible From: header.
- SPF alignment — the domain used in the SMTP
MAIL FROMenvelope must align with theFrom:header domain. - DKIM alignment — the
d=tag in the DKIM signature must align with theFrom:header domain. - A message passes DMARC if it passes SPF with alignment or DKIM with alignment. Both do not need to pass.
What aggregate reports contain
When you include an rua address, receiving mail providers (Gmail, Microsoft, Yahoo, and others) send you daily XML reports at the end of each reporting interval. Each report contains:
- The source IP address that sent the messages.
- The number of messages from that IP.
- Whether SPF, DKIM, and DMARC passed or failed for each source.
- The disposition applied (none, quarantine, or reject).
These reports are invaluable for discovering legitimate sending sources you may have forgotten (marketing platforms, CRMs, transactional email services) and for detecting spoofing attempts before you move to a strict policy.
DMARC report analysis tools
The raw XML reports are dense and difficult to read directly. Several tools can parse and visualize them:
- Postmark DMARC — free hosted report aggregation and visualization.
- dmarcian — commercial platform with a free tier for low-volume domains.
- parsedmarc — open-source self-hosted CLI and Elasticsearch/Kibana pipeline.
- DMARC Digests — lightweight free service that emails you a human-readable summary.
Common mistakes to avoid
- Jumping straight to
p=rejectbefore reviewing reports typically blocks legitimate mail from unregistered sending services. - Setting
adkim=s(strict) will break DKIM for any subdomain-signed messages, including many ESPs that sign from a subdomain of your domain. - Forgetting to add SPF records and DKIM signatures for third-party senders (Mailchimp, Salesforce, Zendesk, etc.) before enforcing DMARC.
- Only one DMARC record per domain is allowed. Multiple
_dmarcTXT entries cause the record to be treated as invalid.