# DMARC record generator

> Writes a DMARC record to RFC 9989, with report addresses, alignment and test mode. Free, no signup. Runs in your browser. Nothing you type is sent to us.

**DMARC record generator. A DMARC record to the current standard, in seconds, no signup.** Use it at https://tools.joinvalley.co/dmarc-record-generator

## What goes in a DMARC record? Every tag in RFC 9989, and the three it removed.

A DMARC record is a TXT record at _dmarc.yourdomain that starts with v=DMARC1 and says what receivers should do with mail that fails (p=) and where to send reports (rua=). RFC 9989 removed pct=, rf= and ri=; t=y replaces pct=0.

| Tag | What it sets | Default |
| --- | --- | --- |
| v= | Version, always DMARC1, and always first | Required |
| p= | Policy for the domain: none, quarantine or reject | none |
| sp= | Policy for subdomains that exist | Same as p= |
| np= | Policy for subdomains that don't exist (new) | Same as sp=, then p= |
| t= | Test mode: y asks receivers to apply one level lower (new) | n |
| rua= | Where aggregate reports go | No reports |
| ruf= | Where failure reports go | No reports |
| fo= | When failure reports are made: 0, 1, d or s | 0 |
| adkim= | DKIM alignment: relaxed or strict | r |
| aspf= | SPF alignment: relaxed or strict | r |
| psd= | Whether the domain is a public suffix (registries only) | u |
| pct=, rf=, ri= | Removed in RFC 9989. Use t=y where you used pct=0. | Not used |

From RFC 9989 section 4.7 and Appendix C.5.2. Receivers ignore tags they don't know, so old tags do no harm, but they do nothing either.

Sources: [RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC)](https://www.rfc-editor.org/rfc/rfc9989) (read 2026-11-09)

## How it works

Type your domain, pick a policy and add a report address; open More options for subdomain policies, alignment, test mode and failure reports. The record updates as you go. Everything runs in your browser.

It writes tags in RFC 9989's form: v=DMARC1 first, then p=, then only what differs from the defaults, so the record stays short. If a report address is on another domain, it also writes the record that domain must publish to accept your reports.

The checks say what the record will actually do: p=none with no report address does nothing you can see, and test mode lowers the policy one step only at receivers that follow RFC 9989.

What it can't know is whether your mail passes yet. Start at p=none with reports, read them, and move to quarantine and reject once your real senders pass SPF or DKIM with alignment.

## Roll out DMARC without losing real mail. What changed in RFC 9989, and the order we'd go in.

DMARC tells receivers what to do when mail claiming to be from you fails SPF and DKIM. Here's how we'd set it.

### Gmail asks bulk senders for DMARC

Gmail's sender guidelines require DMARC from anyone sending more than 5,000 messages a day to Gmail accounts, along with both SPF and DKIM. They say the policy can be set to none, so a monitoring record meets the requirement.

Sources: [Gmail Help: Email sender guidelines](https://support.google.com/a/answer/81126) (read 2026-11-09)

### Start at none, with reports

With p=none receivers take no action, and with rua= they send you daily aggregate reports of everything sent as your domain. Without rua= you get no reports at all. We'd run p=none with reports until every service that sends for you passes, then step up to quarantine, then reject.

Sources: [RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC)](https://www.rfc-editor.org/rfc/rfc9989) (read 2026-11-09)

### pct= is gone; t= replaces it

RFC 9989, which obsoletes RFC 7489, removed pct= because it was rarely applied accurately except at 0 and 100. t=y works like pct=0: receivers apply one level lower. Receivers still on RFC 7489 ignore tags they don't know, so to them t=y means nothing and the policy applies in full.

Sources: [RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC)](https://www.rfc-editor.org/rfc/rfc9989) (read 2026-11-09), [RFC 7489: DMARC (obsoleted by RFC 9989)](https://www.rfc-editor.org/rfc/rfc7489) (read 2026-11-09)

### Reports to a DMARC service

When rua= points at another domain, that domain must publish a TXT record at yourdomain._report._dmarc.theirdomain with the value v=DMARC1; before receivers send reports there. Services that collect DMARC reports normally publish it for their customers.

DMARC protects your name. Getting replies is the other half. [Valley](https://www.joinvalley.co/?utm_source=tools_suite)

Sources: [RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC)](https://www.rfc-editor.org/rfc/rfc9989) (read 2026-11-09)

## Sources

- [RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC)](https://www.rfc-editor.org/rfc/rfc9989) (read 2026-11-09)
- [RFC 7489: DMARC (obsoleted by RFC 9989)](https://www.rfc-editor.org/rfc/rfc7489) (read 2026-11-09)
- [Gmail Help: Email sender guidelines](https://support.google.com/a/answer/81126) (read 2026-11-09)

## Questions people ask

### What is a DMARC record?

A DNS TXT record at _dmarc.yourdomain that tells receivers what to do with mail that fails SPF and DKIM alignment, and where to send reports about it.

### How do I create a DMARC record?

Pick a policy and a report address here, copy the value, and add it at your DNS host as a TXT record named _dmarc.

### What DMARC policy should I start with?

p=none with a rua= report address. Gmail accepts p=none for bulk senders, and the reports show what to fix before you move to quarantine or reject.

### What's the difference between quarantine and reject?

Quarantine asks receivers to treat failing mail as suspicious, usually sending it to spam. Reject asks them to refuse it.

### Is pct still used in DMARC?

No. RFC 9989 removed pct=, along with rf= and ri=. Use t=y, which works like pct=0.

### What does np= mean in DMARC?

The policy for subdomains that don't exist, new in RFC 9989. If it's missing, receivers use sp=, then p=.

### What is DMARC alignment?

Whether the domain that passed SPF or DKIM matches the From: domain. Relaxed allows the same organizational domain; strict needs an exact match.

### Why aren't my DMARC reports arriving at a third-party address?

The other domain may not have published yourdomain._report._dmarc.theirdomain with v=DMARC1;. This page writes that record for you.

### Is this DMARC generator free?

Yes. It's free, needs no signup and runs in your browser.

## Related tools

- [SPF record generator](https://tools.joinvalley.co/spf-record-generator): Builds an SPF record and counts every DNS lookup, nested includes too, against 10.
- [DKIM record generator](https://tools.joinvalley.co/dkim-record-generator): Makes a DKIM key pair in your browser and writes the TXT record to publish.
- [SPF, DKIM and DMARC checker](https://tools.joinvalley.co/spf-dkim-dmarc-checker): Checks a domain's SPF, DKIM and DMARC records against Gmail and Yahoo's sender rules.
- [Email setup map](https://tools.joinvalley.co/email-setup-map): Draws a domain's email setup as one diagram: MX, the SPF include tree, DKIM and DMARC.
- [Cold email domain finder](https://tools.joinvalley.co/cold-email-domain-finder): Sending domain ideas close to your brand, each checked against its registry.

## Next step

Want replies, not just clean copy? Valley finds buyers showing real buying signals and messages them across email and LinkedIn. [Valley](https://www.joinvalley.co/?utm_source=tools_suite)

Shelf: [04 Email outreach](https://tools.joinvalley.co/email-outreach)

---

Tools by Valley, made by [Valley](https://www.joinvalley.co/?utm_source=tools_suite). HTML version: https://tools.joinvalley.co/dmarc-record-generator
