Generators

DMARC Record Generator

Generate a DMARC policy TXT record for your domain with all options explained.

Policy (p)
Subdomain policy (sp)
Reporting email (rua)
Forensic email (ruf)
Percentage (pct)
Alignment
TXT Record
DNS Name
_dmarc.yourdomain.com

About DMARC Builder

Generates a DMARC policy TXT record, which tells receiving mail servers what to do with messages claiming to be from your domain that fail SPF and DKIM checks — quarantine, reject, or take no action, plus where to send reports. DMARC is what actually turns SPF and DKIM into meaningful anti-spoofing protection. The safe rollout path is starting with p=none (monitor-only) to collect reports and confirm legitimate senders aren't failing, before moving to p=quarantine and eventually p=reject.

The rua tag sets where aggregate summary reports go, while ruf sets forensic per-message failure reports — most receivers only honor rua in practice, since forensic reports contain message content and privacy concerns mean many providers don't send them at all.

📖 Read more in our Knowledge Base →

Rollout Strategy

Start with p=none and an rua address.
Monitor reports for 2-4 weeks.
Move to quarantine at pct=10, increase.
Finally enforce reject at pct=100.

Related Tools

Where the record lives

A single TXT record at _dmarc.example.com. Subdomains without their own record inherit the policy of the organizational domain. A typical starting record:

v=DMARC1; p=none; rua=mailto:dmarc@example.com; adkim=r; aspf=r

The tags

TagMeaning
v=DMARC1Required, and must come first.
pPolicy for failing mail: none (monitor only), quarantine (spam folder), reject (refuse).
spSeparate policy for subdomains.
ruaWhere daily aggregate reports go. The most useful tag after p.
rufPer-message failure reports. Few receivers send them.
adkim / aspfAlignment mode for DKIM / SPF: r relaxed (default) or s strict.

A safe rollout

  1. Publish p=none with rua and collect reports for two to four weeks. The guide How to read DMARC reports explains them.
  2. Find every legitimate source that fails and fix its SPF or DKIM alignment. The SPF/DKIM/DMARC checker shows the current state.
  3. Move to p=quarantine, watch the reports again, then p=reject.

Gmail and Yahoo require at least p=none from bulk senders. p=none protects nothing, though: spoofed mail is still delivered. The goal is reject.

Reports sent to another domain

If rua points to a mailbox at a different domain (for example a reporting service), that domain must authorize it with a TXT record such as example.com._report._dmarc.reports.example.net containing v=DMARC1. Reporting services publish this for you; for your own second domain, add it yourself.