DMARC record generator
A DMARC record is a TXT record published at _dmarc.yourdomain.com that tells receiving servers what to do with mail that fails SPF and DKIM alignment. Choose a policy and a report address below, copy the record, add it at your DNS host, then check it is live.
Fill in the options, or load an example.
Your DMARC record
- Type
- TXT
- Name
- _dmarc
v=DMARC1; p=none
Monitor for two to four weeks, fix every legitimate sender that fails, then move to quarantine.
- Heads up: No rua address: you will get no aggregate reports, so you cannot see who sends as your domain.
Check it is live
The record is built in your browser. The live check asks Cloudflare's public DNS resolver (Google's if Cloudflare does not answer) for _dmarc.yourdomain; nothing you enter is sent to RelayMail.
How to use it
- Enter your domain. A bare domain like example.com works; a pasted email address or URL is cleaned up for you.
- Start with the none policy and add a report address you can read, such as dmarc@yourdomain.com. Reports are how you find senders you forgot about.
- Copy the TXT record and add it at your DNS host as a TXT record named _dmarc, or use the zone-file line if your host takes one.
- Press "Check live record" to look the record up over DNS-over-HTTPS and compare it to what you generated.
- After a few weeks of clean reports, move the policy to quarantine, raise pct step by step, then move to reject.
What each setting does
p is the policy for mail that fails DMARC. none only reports, quarantine asks receivers to treat it as suspicious (usually spam folder), reject asks them to refuse it. sp does the same for subdomains and defaults to p when left out.
pct applies the policy to a share of failing mail so you can ramp up slowly; the rest gets the next softer treatment. rua is where aggregate XML reports go, daily by default. adkim and aspf choose relaxed (subdomains may align) or strict (exact domain match) alignment for DKIM and SPF.
DMARC passes when SPF or DKIM passes and the passing domain aligns with the visible From domain. If you send through a service, make sure it signs with your domain or uses a custom return-path before you tighten the policy.
Questions
Where do I publish the DMARC record?
As a TXT record on the name _dmarc under your domain, for example _dmarc.example.com. Many DNS hosts want only the host part (_dmarc) in the name field and add the domain for you. Publish one record per domain; two DMARC records make receivers ignore both.
Which policy should I start with?
Start with p=none and a rua address. It changes nothing about delivery while the reports show you every service sending as your domain. Once the legitimate ones pass, move to quarantine and then reject.
Do I need DMARC to send email to Gmail and Yahoo?
Gmail and Yahoo require SPF, DKIM and a DMARC record of at least p=none from bulk senders, and a published record is good practice for any domain that sends mail. See their sender guidelines linked below for the current thresholds.
Can my report address be on a different domain?
Yes, but the domain that receives the reports has to publish a permission record, a TXT at yourdomain.com._report._dmarc.reportdomain.com containing v=DMARC1. Without it many receivers skip sending reports. The simplest fix is a rua address on your own domain.
How long until the record takes effect?
Most DNS changes are visible within minutes, but caches can hold the old answer for as long as the previous TTL. If the check says the record is missing right after you add it, wait a few minutes and run it again.
Should I add ruf forensic reports?
Usually not. Few mailbox providers send them because they can contain message content, and aggregate reports from rua already show which sources fail. The generator leaves ruf off unless you add an address.
See also
More free email tools
Updated .
