What the builder does
A DMARC record tells receiving mail servers what to do with mail that claims to be
from your domain but fails SPF and DKIM, and where to send
reports about who is sending in your name. It is one TXT record at _dmarc under your domain. This builder
writes it from a few choices, explains each setting, and gives you a rollout plan so you can tighten the
policy without losing real mail on the way.
Choosing your settings
- Policy is what receivers do with mail that fails:
nonedelivers it and reports it,quarantinesends it to spam, andrejectrefuses it. - Subdomain policy sets a different policy for subdomains. Leave it empty to use the main policy, which is what most domains want.
- Percentage applies quarantine or reject to part of the failing mail while you roll it out. 100 is the default and is left out of the record.
- Report addresses receive the daily aggregate reports. Enter plain email addresses; the builder adds
mailto:for you. - Under More options you'll find failure report addresses, alignment (relaxed by default) and when failure reports are sent.
The record updates as you change a setting. Copy the name and value into your DNS host, or paste the zone file line.
The rollout plan
Going straight to reject is how real mail gets lost: a forgotten newsletter tool or a help desk that
signs with its own domain suddenly stops reaching anyone. The builder shows the record for each of three
stages, with your report addresses in every one:
- Monitor with
p=none. Read the reports for two to four weeks and fix SPF or DKIM for any real sender that fails. - Quarantine once your own mail passes. Failing mail goes to spam, where you can still spot mistakes.
- Reject after a few quiet weeks. Forged mail is refused before it reaches anyone.
Reports on another domain
If a report address is on a domain other than yours, such as a report service, that domain has to agree to receive your reports by publishing a small TXT record. Receivers check for it and skip the address when it is missing. When you enter your domain, the builder lists the exact record each external report domain must publish. Most report services publish it for their customers automatically; for a domain you run yourself, add it there.
Choices worth a second look
The builder never refuses a working choice, but it points out the ones that are easy to get wrong: a policy that only monitors, a percentage below 100, no report address, a weaker policy for subdomains than for the domain, failure reports, and strict alignment. Each one is explained in the result.
What the result gives you
Next to the record you'll find where it goes (_dmarc under your domain), its type, a copy button for each,
and a zone file line for DNS hosts that take those. Below come the rollout plan with the record for every
stage, the authorization records for external report addresses, and the findings, each explained with a
link to a step-by-step guide. Nothing is published for you, and nothing you type is stored: the builder
works the record out and forgets it.
After you publish
DNS changes take effect once the old record's TTL has passed, usually within an hour. Aggregate reports start arriving a day or two after that, one file per receiver per day. A report service turns them into charts; reading the raw files works too, just slower.
Checking what you have now
To see the record your domain publishes today and whether its report addresses have agreed, run the DMARC checker. From its result, Change this policy in the DMARC builder brings your current settings here. When you're done, run the full email check to see SPF, DKIM and DMARC graded together, and use the SPF builder if SPF needs work first.