Skip to content
DMARC Pulse

DMARC generator

DMARC Record Generator

Choose your policy and where reports should go, and create a valid DMARC record to paste into your DNS.

Sign up free to get your own DMARC Pulse address — reports become a readable dashboard instead of XML in your inbox.

Advanced options

Optional. Few providers send them and they may contain personal data.

What to do with the result

You have a record ready to publish

Create one TXT record (a text entry in your DNS) with the host and value shown. If that name already holds a DMARC record, edit it. When receivers (the mail servers that get your messages) find two DMARC records at one name, they discard them all and none applies (RFC 9989, Section 4.10). If you paste the full host into a panel that adds the domain by itself, the name becomes _dmarc.example.com.example.com. After saving, run the DMARC Checker on your domain. If it finds nothing, check the name and give the change time to appear in DNS.

The policy is p=none

With p=none you ask for reports and request no change in how receivers treat mail that fails DMARC. Start here and stay here while you read the reports. Each one typically covers a single UTC day, so expect the first ones a day or more after publishing. Use them to find every service that sends as your domain, then fix the ones that fail. RFC 9989 warns that this can take many months, depending on how often you send. Move on only when your legitimate mail passes.

The policy is p=quarantine or p=reject

These policies ask receivers to treat failing mail as suspicious or to refuse it, so an error here can stop real mail. Publish them only after a period at p=none, once reports show every legitimate sender passing. The policy also covers subdomains unless you set sp. With p=reject, sign all mail with DKIM (a signature on each message). Forwarding usually breaks SPF (the list of servers that may send for you), and RFC 9989, Section 7.4, says not to rely on SPF alone. It also says domains whose users post to mailing lists should not use p=reject.

The report address was left out or is on another domain

The tool drops anything it cannot read as an e-mail address and shows a warning. Without rua, the tag that names the report mailbox, receivers must not send aggregate reports (RFC 9989, Section 4.7). Correct the address and generate again. An address on another organizational domain (normally the domain you registered) needs that domain’s consent. Its owner publishes a TXT record at example.com._report._dmarc.reports.example.net containing v=DMARC1. Without it, receivers ignore the address (RFC 9990, Section 4). The DMARC Checker warns when that record is missing. A host of just _dmarc means the domain was blank or invalid.

The record contains pct or ri

The advanced options add pct when you apply quarantine or reject to under 100% of mail, and ri when you change the interval from 86400 seconds. RFC 9989 removed both tags and its registry marks them historic. Some provider guides still describe pct, so assume the policy reaches all failing mail. To drop both tags, enter 100 and 86400 and generate again. For a trial, RFC 9989 defines t=y, a test flag that asks receivers for a policy one level lower. A receiver that follows only the older RFC 7489 ignores this tag and applies the policy as written, so add it only after reports at p=none show your legitimate mail passing. Add it by hand, because this tool does not.

Explained

Which policy should I choose?

Without reports, choose none for a new record. If a record already exists, keep its policy while adding reporting. Consider quarantine only after every legitimate source passes. Reject needs a separate assessment: RFC 9989 advises against it for domains whose users post to mailing lists. Do not rely on legacy pct to limit the impact.

Where to publish it

Add a TXT record named _dmarc (some DNS panels need _dmarc.yourcompany.com) with the generated value. Then check it with the DMARC Checker.

Frequently asked questions

What is the simplest valid DMARC record?
v=DMARC1; p=none; rua=mailto:reports@yourcompany.com — a monitoring policy with a reporting address.
Can I send reports to more than one address?
Yes, separate them with commas. Addresses on another domain need that domain to authorize your reports.
Should I use strict alignment?
Usually not. Relaxed alignment accepts subdomains (mail.yourcompany.com), which most email services need.
Do I need forensic (ruf) reports?
No. Aggregate reports are enough to monitor and enforce DMARC.

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.

Related tools