Vector Mail records Header analyser →

Stop people sending mail as you.

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.

Your domain

The domain your mail comes from. Use the root domain, not a subdomain.

What should receivers do with mail that fails?

This is the whole point of DMARC. Everything else is detail.

Where should reports go?

Without a reporting address DMARC tells you nothing, and you're publishing a policy blind.

Per-message reports that can contain subject lines, headers and recipient addresses. Most receivers ignore these, and they carry real privacy weight. Leave off unless you have a specific reason.

Fine tuning

The defaults here are the right answer for almost everyone.

Mail claiming to come from subdomains you never created, like billing.yourdomain.com. Nothing legitimate sends from these, so reject is safe even while you're still monitoring everything else.
Mail from subdomains that do exist. Leave inherited unless they need a different policy. Ignored if you publish this record on a subdomain rather than your root domain.
Asks receivers to apply one level below your stated policy, so you can publish a policy and watch the reports without it biting yet.
Relaxed lets a subdomain signature count for the parent domain. Strict demands an exact match.
Same idea for SPF. Strict breaks a lot of legitimate third-party senders, so relaxed is the sane default.
Public suffix declaration and failure reporting options. You almost certainly don't need these.

Your record

Add this as a TXT record in your DNS.

Host
_dmarc
Type
TXT
TTL
3600 (or your provider's default)

Getting to reject without breaking anything

DMARC goes wrong when people jump straight to the end. Each stage wants a few weeks of reports behind it.

Copied