Build a DMARC record that is correct the first time.
Choose a policy and a place for the reports. The record is written as you click, with the host name, the value, and the steps for your DNS provider. No syntax to memorize, and no way to put the tags in the wrong order.
Five choices. Only two of them are hard.
The record is one line of text. The thinking is in which policy to start with and who reads the reports.
- Policy (p)
- none, quarantine, or reject. Start at none unless your reports already show every sender passing. The trade-offs are in none vs quarantine vs reject.
- Report address (rua)
- Where receivers send daily aggregate reports. Use a SpoofKiller address to read them as a dashboard, or your own mailbox to receive raw XML. What the reports contain.
- Percentage (pct)
- For a staged move to quarantine or reject: apply the policy to a share of failing mail, watch, and raise it. Left at 100, the tag is omitted, since that is the default.
- Subdomain policy (sp)
- What applies to subdomains without their own record, including names that do not exist and that a forger might invent. By default they inherit the main policy.
- Alignment (adkim, aspf)
- Relaxed lets subdomains align with the main domain. Strict requires an exact match and breaks more than people expect. Leave both relaxed unless you know why not. Alignment explained.
- External report authorization
- If your report address is at another domain, that domain has to publish a one-line record accepting your reports. The generator shows the exact name when it applies.
The safest DMARC record is the one that asks questions first.
There is a temptation, on learning that p=reject is the strong setting, to publish it and be done. Resist. A reject policy tells every receiver to refuse mail that fails authentication, and at this moment you do not know how much of your own mail fails. The newsletter tool nobody configured, the invoicing system sending through a vendor’s servers, the scanner in the back office: each will be turned away, silently, and the first report will come from a customer who did not get an invoice.
So the standard order is dull and correct. Publish p=none with a reporting address. Read the reports for a few weeks. Fix each legitimate sender, which usually means turning on DKIM signing with your own domain at that service. Then move to quarantine, then reject. The whole route is in how to reach p=reject, and provider-specific steps are in the guides for Google Workspace and Microsoft 365.
DMARC also assumes SPF and DKIM exist. Before publishing, confirm both with the SPF checker and DKIM checker. If you already have a DMARC record, do not add a second: edit the one you have, after reading it in the DMARC checker. Two records cancel each other out.

How generated records still go wrong.
The record will be valid. These are the ways a valid record ends up doing nothing.
Published at the root instead of _dmarc
The TXT record's name must be _dmarc. At the bare domain it is just a piece of text. If your DNS host shows the name as _dmarc.example.com.example.com afterward, remove the domain you typed.
A second DMARC record added beside the first
Receivers that see two discard both. Replace the existing record's value instead of creating a new record.
The value pasted with smart quotes or line breaks
Paste as plain text on one line. Most DNS hosts add the surrounding quotation marks themselves.
Reports sent to a mailbox nobody opens
Aggregate reports are XML, compressed, and plentiful. If no one will read them, send them to an analyzer. A single file can be read with the DMARC report analyzer on this site.
Enforcement before the senders were fixed
If legitimate mail starts failing after you tighten the policy, go back one step, find the failing source in your reports, and fix its SPF or DKIM alignment before trying again.
Reports never arrive
Allow a day or two; most receivers send once daily. If the address is at another domain, check the authorization record. Then confirm the record is visible with the propagation checker.
How to create a DMARC record
Generate a valid DMARC TXT record and publish it in DNS.
- 1
Choose a policy
Select p=none to begin monitoring without affecting delivery. Choose quarantine or reject only when reports show all legitimate mail passing.
- 2
Set the report address
Use your SpoofKiller reporting address or enter your own mailbox for the rua tag.
- 3
Copy host and value
Copy the host name _dmarc and the generated value using the copy buttons.
- 4
Add the TXT record
At your DNS provider, create a TXT record with that name and value, or edit the existing DMARC record if there is one. Then verify it with the DMARC checker.
Questions about this tool
Straight answers. If yours is not here, ask us and a person will reply.
Want a second pair of eyes before you publish?
Send us your domain and the record you plan to use. We will check it against what is already in your DNS and tell you if anything will break.
- A person reads every message
- No sales sequence, no list rental
- Reply within one business day
The record asks for reports. Have somewhere to read them.
Create a free account to get the reporting address for your domain and see your DMARC reports as a dashboard, not as attachments.
Related tools and guides
- DocsDMARC Reporting SetupAdd your unique reporting address to the rua tag and confirm that reports arrive.Read
- GuideDMARC for Cloudflare DNSHow to add and verify email authentication records in Cloudflare DNS, including the proxy and CNAME pitfalls.Read
- GuideDMARC for Google WorkspaceSet up SPF, turn on DKIM signing, and publish DMARC for a domain that sends mail through Google Workspace.Read
- GuideDMARC for Microsoft 365Configure SPF, enable DKIM for your custom domain, and publish DMARC for mail sent through Microsoft 365.Read
- SpoofKillerDocumentationSetup guides, feature references, and the API.Read
- DocsAlerts and NotificationsAlert types, severity thresholds, digests, and how duplicates are suppressed.Read
