Configuring DMARC takes about twenty minutes. Fifteen of them are spent trying to remember who has the login for your DNS. The record itself is one line of text, shorter than most email signatures, and the entire procedure is: write the line, paste it into the right box, and check that the internet can see it.
People still get it wrong, usually in one of five ways, all of them avoidable. This guide goes from no record to a published, verified one, and stops along the way at each of the places where the five mistakes are made.
Before you start
You need three things.
- Access to your domain’s DNS. That means wherever your nameservers are hosted: your registrar, a DNS provider, or your web host. If you are unsure, a DNS security check lists the nameservers, which usually gives it away.
- A look at what is already there. Run the DMARC checker on your domain. If a record exists, you will be editing it, not adding a second one.
- Somewhere for reports to go. A dedicated mailbox, or the address of a reporting service. Not your own inbox, unless you enjoy compressed XML with your morning mail.
You do not need SPF and DKIM to be perfect first. A monitoring-only DMARC record is harmless without them, and its reports are the fastest way to learn what needs fixing. If you want to see their current state anyway, the domain health check covers all three.
Step 1: Write the record
For a first record, this is all you need:
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.comTags are separated by semicolons. v=DMARC1 must come first and p= second; the rest may follow in any order. The DMARC record generator will assemble the line from a few choices if you prefer not to type it. Here is the full vocabulary:
| Tag | Purpose | Values | If omitted |
|---|---|---|---|
v | Version. Required, first | DMARC1 | Record is invalid |
p | Policy for the domain. Required | none, quarantine, reject | Record is invalid |
rua | Where to send aggregate reports | One or more mailto: addresses, comma-separated | No reports |
sp | Policy for subdomains | Same as p | Subdomains use p |
pct | Percentage of failing mail the policy applies to | 0 to 100 | 100 |
adkim | DKIM alignment mode | r relaxed, s strict | Relaxed |
aspf | SPF alignment mode | r relaxed, s strict | Relaxed |
ruf | Where to send failure reports | mailto: addresses | None requested; few receivers send them regardless |
fo | When to generate failure reports | 0, 1, d, s | 0 |
ri | Requested interval between aggregate reports, in seconds | A number | 86400 (one day) |
Leave the alignment modes at relaxed unless you have a specific reason; strict mode breaks senders that sign with a subdomain. Relaxed and strict alignment are explained separately. And start with p=none. The case for that, and for what comes after, is made in none vs quarantine vs reject.
Step 2: Publish it in DNS
In your DNS provider’s control panel, add a new record with these values:
| Field | Value |
|---|---|
| Type | TXT |
| Name / Host | _dmarc |
| Value / Content | v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com |
| TTL | 3600 (one hour), or the provider’s default |
Three things to watch at this step.
The host name. Most control panels append your domain automatically, so you enter _dmarc and the record is created at _dmarc.example.com. A few expect the full name. If you enter the full name where the short one was wanted, you get _dmarc.example.com.example.com, which is a valid record that no receiver will ever look for. The leading underscore is required.
One record only. There must be exactly one DMARC TXT record at _dmarc. If two exist, receivers discard both, and you have no policy. If the checker found an existing record, edit it.
Quotation marks. Most panels add the surrounding quotes for you. If yours shows the value wrapped in two sets, remove one.
If your DNS is at Cloudflare, the Cloudflare DNS guide has the screen-by-screen version.
Step 3: Check your work
Do not take the control panel’s word for it. Ask DNS directly. From a terminal:
dig +short TXT _dmarc.example.com
nslookup -type=TXT _dmarc.example.comEither should return your record:
"v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"Or skip the terminal and run the DMARC checker again, which also validates each tag and flags the mistakes listed below. New records are usually visible within minutes. If one resolver sees the record and another does not, the DNS propagation checker queries several public resolvers at once and shows which are behind.
A record you have not looked up is a record you hope you published.
Step 4: Make sure the reports arrive
Within a day or two, aggregate reports should begin to appear at the rua address. If they do not, the usual suspects are a missing mailto: prefix, a typo in the address, or a mailbox that refuses compressed attachments.
There is one further requirement when the reporting address is at a different domain from the one being protected, as it will be if you use a reporting service or collect reports for several domains in one place. The destination domain must publish a record authorizing it to receive reports about yours:
example.com._report._dmarc.reports.vendor.example. TXT "v=DMARC1"Without it, receivers that follow the standard will not send reports to that address. Reporting services publish this on their side as a matter of course, so there is normally nothing for you to add; the DMARC reporting setup guide shows the exact address to use. To send reports to two places, list both:
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com,mailto:abc123@reports.vendor.exampleSubdomains and other domains
One record at the organizational domain covers every subdomain that has no DMARC record of its own. When mail claims to be from billing.example.com, a receiver looks for _dmarc.billing.example.com first and falls back to _dmarc.example.com. So you do not need a record per subdomain, though you may publish one where a subdomain needs different treatment.
Other domains are another matter. Each registered domain needs its own record; nothing carries over from example.com to example.net. For domains that send no mail at all, skip the monitoring phase and go straight to the end state:
example.net. TXT "v=spf1 -all"
_dmarc.example.net. TXT "v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.com"The five usual mistakes
- Publishing at the wrong name. The record sits at the bare domain, or at
dmarcwithout the underscore, or at a doubled name. Receivers look only at_dmarc. - Two DMARC records. Often one from years ago and one new. Both are ignored.
- Syntax slips. Commas where semicolons belong,
p=monitoror another value that does not exist, a missingmailto:, orv=DMARC1anywhere but first. - No reporting address.
v=DMARC1; p=noneis valid and tells you nothing. It is a policy of doing nothing, about information you have declined to receive. - Starting at reject. On a domain that sends mail, an enforcing policy before you have seen a single report is a bet that you know every sender. Almost nobody wins it.
What happens next
Publishing the record is the easy part and the beginning of the useful part. Over the next few weeks the reports will show which services send as your domain and which of them fail. Fix those, typically by enabling DKIM with your own domain at each service; the guides for Google Workspace and Microsoft 365 cover the two most common mail systems. Then raise the policy in stages, following the plan for reaching p=reject.
If you would like the reports read for you, getting started with SpoofKiller takes about as long as the record did: add the domain, verify it, and add one address to your rua tag. On plans with DNS monitoring, scheduled checks also watch the record itself, so that if someone edits it by accident you hear about it from us and not from a bounced invoice. The pricing page lists what each plan includes.

