Email Marketing & AutomationMartech Zone AppsMartech Zone Builders

App: Import, Modify, or Build Your DMARC TXT Record from Scratch

Most teams publish a policy once and then stop looking at it. A phone number in the directory changes, a new sending service goes live, and the record at the DNS host still describes last year’s setup.

A DMARC record is the DNS TXT value at _dmarc. It names the policy for mail that fails alignment, and the mailboxes that should receive reports. The generator on this page loads the currently published record, or accepts a pasted value, and rebuilds the line as you change it. Copy the result into DNS yourself. The page does not edit your domain.

DMARC Record Generator v1.0.3Last Update: Oct 9, 2026

Enter a domain to load its current DMARC record, or paste a record and edit it here.

Optional — Enter a domain to look up the TXT record at _dmarc, or paste a record that starts with v=DMARC1.
Optional — The domain you send mail from. The record is published on _dmarc under this name. It is not part of the TXT value.
Required — What a receiver should do when a message fails DMARC. None monitors only. Quarantine asks for spam. Reject asks the receiver to refuse the message.
Optional — Share of failing messages the policy applies to. 100 means all of them. A lower number is a way to test quarantine or reject on a sample.
Optional — Policy for subdomains that do not publish their own DMARC record. Leave this as Same as domain to omit the tag.
Optional — Relaxed passes when the DKIM signing domain shares the organizational domain with the From address. Strict requires an exact domain match.
Optional — Relaxed passes when the SPF-authenticated domain shares the organizational domain with the From address. Strict requires an exact domain match.
Optional — Mailboxes that should receive daily aggregate reports. These are the rua addresses. Leave blank only if you do not want reports.
Optional — Mailboxes for per-message failure reports, the ruf tag. Many receivers send few or none of these. Optional.
Optional — When to ask for a failure report. 0 is the default and is omitted. 1 asks on any underlying SPF or DKIM failure.
Optional — How often receivers should send aggregate reports, in seconds. Leave this blank to omit the tag. Receivers use 86400, one day, when it is absent.
Tags this form does not edit, kept so an import does not drop them. Example: np=reject
The TXT value to publish. The host name is separate and is not part of this string.

Copy DMARC Record

Was this helpful?

Change the Policy Before You Publish It

Start from the record the lookup returns. If the policy is p=none, receivers are being asked to deliver the mail and send reports. Quarantine asks them to treat a failure as spam. Reject asks them to refuse it. Move from none to a stricter policy only after the reports show that your own mail is aligned.

Alignment is the part people skip. A message passes when SPF or DKIM passes, and that passing domain matches the visible From domain. Relaxed alignment, the default, allows a shared organizational domain. Strict alignment requires an exact match. The percentage tag applies the policy to a sample of failing mail, letting you test quarantine or reject before it affects every failure.

Aggregate reports, called RUA, are the daily XML files. Failure reports, RUF, are the per-message notes, and many receivers send few of them. A logo in the inbox depends on BIMI, which can’t display when the authentication under it is missing.

The Other DMARC Guides

The generator is the record itself. These pages cover the reports, the neighboring records, and the setup checks around it.

Look up the record, change only the tags you mean to change, and publish one TXT value at _dmarc. Then read the next report before you tighten the policy again.

Related Articles