Skip to content

Free tool

DMARC record generator

Choose a policy, add where reports should go, and copy the DMARC record for your domain. Free, no signup.

DMARC record options

Policy (p)
Subdomain policy (sp)

100 applies the policy to all failing mail.

Where receivers send daily reports. Separate several addresses with commas.

Few receivers send these, and they can contain message content.

DKIM alignment (adkim)
SPF alignment (aspf)
Failure report options (fo)

Only used when a ruf address is set.

Your DMARC record

Name (TXT record)

_dmarc.shipmail.to

Value

v=DMARC1; p=none
  • No aggregate report address (rua)

    Without rua you get no reports, so you cannot tell when it is safe to move to quarantine or reject.

    Warning

Published your record? Confirm receivers can read it with the free DMARC checker

Once reports arrive at your rua address, open them with the free DMARC report reader

Roll out in three steps

Start at p=none with a rua address. Nothing changes for your mail, but receivers send you daily reports listing every server that sends as your domain and whether it passed SPF or DKIM.

When the reports show all your legitimate mail passing for a few weeks, move to p=quarantine. Failing mail goes to spam. You can apply it gradually by raising pct from 25 to 100. RFC 9989 (May 2026) replaces pct with t=y, a test mode, but Google's rollout guide still uses pct and receivers ignore tags they do not know.

Once quarantine causes no problems, move to p=reject. Receivers refuse spoofed mail before it reaches anyone. This is the policy to end on.

What the tags mean

sp sets a separate policy for subdomains; without it they follow p. adkim and aspf choose the alignment mode. Relaxed lets mail.yourdomain.com count for yourdomain.com, strict needs an exact match.

ruf asks for failure reports about single messages. Few receivers send them, and they can contain message content, so most domains leave ruf out. fo picks which failures trigger such a report.

Publish and check it

Add a TXT record named _dmarc on your domain, which is _dmarc.yourdomain.com, with the generated value. Replace any existing DMARC record. Receivers ignore DMARC entirely when a domain publishes two.

Then run the DMARC checker to confirm receivers can read the record, and come back here when your reports say it is time for the next step.

FAQ

Questions?

Talk to a human →
Which policy should I start with?

p=none with a rua address. It changes nothing for delivery and shows you every service sending as your domain, so you can fix SPF and DKIM before enforcing.

How long should I stay on p=none?

Long enough to see every sender in your aggregate reports, usually two to four weeks. Then move to p=quarantine, and later to p=reject.

Can reports go to an address on another domain?

Yes, but the other domain has to accept them by publishing a TXT record v=DMARC1 at yourdomain.com._report._dmarc.otherdomain.com. DMARC report services set this up for their customers.

Should I use strict alignment?

Usually not. Relaxed alignment accepts subdomains such as mail.yourdomain.com, which many sending services use. Choose strict only if every message is sent and signed with your exact domain.

Will p=reject block forwarded mail?

Forwarding breaks SPF, but DKIM signatures usually survive it, so forwarded mail still passes DMARC when you sign with DKIM. Make sure every sender signs with your domain before moving to reject.

Email, newsletters and booking pages on your own domain, in one plan.

Get started for free