Free tool

DMARC record generator

Choose a policy and where the reports go, and copy a DMARC record that follows RFC 9989, the DMARC standard of May 2026. It runs in your browser: nothing is looked up or sent.

What the tags mean

v=DMARC1
The version. It has to be the first tag, written exactly like this, or receivers ignore the whole record.
p
The policy for mail that fails DMARC: none (only report), quarantine (spam folder) or reject (refuse).
sp and np
The policy for subdomains that exist (sp) and for names that do not exist at all (np). Without them, p applies.
rua
Where receivers send aggregate reports: a daily overview of the servers that sent mail in your name and whether they passed.
ruf and fo
Where receivers send a report per failing message, and when (fo). Few large receivers send them.
adkim and aspf
Whether a subdomain may stand in for the domain when DKIM or SPF passes (r, relaxed, the default) or only the exact domain (s, strict).
t
Test mode. With t=y receivers apply one level below the policy. It replaces the old pct tag.

From none to reject

  1. Set up SPF and DKIM. DMARC passes when SPF or DKIM passes for the domain in the From address. See SPF and DKIM.
  2. Publish p=none with a report address. Read the reports for a few weeks and find every service that sends in your name.
  3. Fix the senders that fail. Add them to SPF, or switch on DKIM signing for them.
  4. Move to quarantine, then reject. Use t=y for a first step if you are unsure, and keep reading the reports.

Keep it working

A DMARC record is edited by hand, and a DNS move or a second record added by a new service quietly breaks it: with two records, receivers ignore both. The DMARC record check of DoubleCheck reads your record every day and alerts you when the policy gets weaker, the report address disappears or the record becomes invalid.

FAQ

Frequently asked questions

Which policy should I start with?

With p=none and a report address. Nothing is blocked yet, and the reports show every server that sends mail in your name. Fix the senders that fail, then move to quarantine and finally to reject.

What happened to pct?

RFC 9989 retired the pct tag, together with rf and ri: receivers ignore them. To try a stricter policy without its full effect, use t=y (test mode): receivers then apply one level below the policy you publish.

Can I send the reports to another company?

Yes, for example to a DMARC report service. Receivers only send reports to a domain outside your own when that domain publishes a record agreeing to it. The generator shows that record; most report services publish it for you.

Does this generator look up my domain?

No. Everything happens in your browser. Nothing is looked up or sent anywhere, so it also works for a domain that has no record yet.

How do I know my record keeps working?

Records get changed by hand, by DNS moves and by providers. The DMARC record check reads your record every day and alerts you when the policy gets weaker, the report address disappears or a second record appears.

The standard behind this generator

DMARC is defined by three RFCs of the IETF, published in May 2026 on the Standards Track. Together they replace RFC 7489 from 2015, which was only informational:

  • RFC 9989, the DMARC protocol. It also replaces RFC 9091, the experimental extension for public suffix domains.
  • RFC 9990, aggregate reporting (rua).
  • RFC 9991, failure reporting (ruf).

The generator applies these requirements:

Where the record lives
A TXT record on the domain with _dmarc in front of it, such as _dmarc.example.com (RFC 9989, sections 4.1 and 4.5). When a name has more than one DMARC record, receivers discard all of them (section 4.10).
The version first
v=DMARC1 must be the first tag, with exactly that value; otherwise the whole record is ignored (section 4.7). Tags are separated by a semicolon (section 4.8).
The tags
The tags in use are v, p, sp, np, adkim, aspf, fo, psd, t, rua and ruf (section 9.3). The generator leaves out a tag when you choose its default: adkim=r, aspf=r, fo=0 and t=n (section 4.7). It always writes p; without it receivers act as if p=none.
Retired tags
pct, rf and ri are marked historic and receivers ignore them (sections 4.7 and 9.3). The generator never writes them. t=y takes over the test use of pct: receivers apply one level below the policy (section 4.7).
Failure report options
fo is ignored when there is no ruf address (section 4.7), so the generator only writes it together with one.
Report addresses
Several addresses are separated by commas, and every receiver must support mailto: addresses (sections 4.7 and 8). A comma or exclamation mark inside an address must be percent-encoded (section 4.8). The size limit !10m of RFC 7489 is obsolete and not written.
Reports to another domain
When a report address is in another organization than your domain, receivers first look for a TXT record your-domain._report._dmarc.report-host that starts with v=DMARC1. Without it they ignore the address (RFC 9990, section 4; RFC 9991, section 5 for failure reports). A record on *._report._dmarc.report-host accepts reports for every domain. The generator checks whether an address is outside your domain, which is stricter than the organization rule: when your report address is at a sister domain of your own, you may not need the extra record.

Not in the generator: psd, which is only for the operators of public suffix domains such as country registries (section 4.7).

Get started

Keep your DMARC record in check

Start with €5 of free credit, no credit card required. Alerts by email, SMS, Slack, Microsoft Teams or Discord.

Start monitoring