Build a DMARC record, and understand what it does before you publish it. Set this up wrong and real invoices stop arriving, so the tool tells you what each choice actually costs.
DMARC follows RFC 9989, the 2026 standard that replaced RFC 7489. pct, ri and rf no longer exist.
The domain your mail comes from. Use the root domain, not a subdomain.
This is the whole point of DMARC. Everything else is detail.
Without a reporting address DMARC tells you nothing, and you're publishing a policy blind.
The defaults here are the right answer for almost everyone.
billing.yourdomain.com. Nothing legitimate sends from these, so reject is safe even while you're still monitoring everything else.Every service that sends on your behalf needs listing, or its mail fails. Pick the ones you use.
Your own servers, and any provider not in the list above.
203.0.113.0/24. These cost no DNS lookups, so they're the cheapest way to authorise a server.include: prefix. Each one costs at least a lookup.a. Only useful if the web server also sends mail — costs a lookup either way.mx. Common, but receiving mail and sending it aren't the same thing — plenty of setups don't need this.Add this as a TXT record in your DNS.
DMARC goes wrong when people jump straight to the end. Each stage wants a few weeks of reports behind it.