DMARC Record Generator

Create a DMARC policy for your domain. Configure enforcement, reporting, and subdomain policies.

Domain

DMARC Policy (p=)

Subdomain Policy (sp=) — optional

Aggregate Reports (rua=)

Forensic Reports (ruf=)

Apply to 100% of messages (pct=)

1%100%100%

Generated DMARC Record

DNS Name (TXT)

_dmarc.example.com

Record Value

v=DMARC1; p=none

Validate this record

What is DMARC?

DMARC (Domain-based Message Authentication, Reporting and Conformance) ties SPF and DKIM together. It tells receiving servers what to do with mail that fails authentication — monitor (none), quarantine, or reject — and where to send reports.

Choosing a policy

Start at p=none to collect reports without affecting delivery, review who is sending as your domain, then tighten to p=quarantine and finally p=reject once legitimate mail passes. This staged rollout protects you from accidentally blocking real email.

Where the record lives

Publish the generated record as a TXT record at _dmarc.yourdomain.com. Add a rua address to receive aggregate reports so you can see exactly which sources pass and fail authentication.

Frequently asked questions

Do I need DMARC?

Yes if you send bulk mail to Gmail or Yahoo (at least p=none). For any domain, DMARC prevents spoofing and improves deliverability.

What policy should I start with?

Start with p=none to monitor, then move to quarantine and reject as you confirm your legitimate senders all pass SPF or DKIM alignment.

What is a rua address?

rua is the email address that receives DMARC aggregate reports — XML summaries of who is sending mail using your domain and whether it passed authentication.

Does DMARC require SPF and DKIM?

DMARC builds on them: a message passes DMARC when it passes SPF or DKIM AND that authenticated domain aligns with the From domain. You need at least one aligned and passing.