No reporting address
Without rua you get no aggregate reporting visibility.
Built for agencies and B2B sales teams.Built for lead generation agencies and B2B sales teams. Manage contacts, automate email sequences, and handle replies in one workspace.
Start free →Create a DMARC TXT record for your domain. Choose a policy, reporting address and alignment settings, then review your record before publishing it in DNS.
Example: DMARC record draft
Pick none, quarantine or reject. Many domains start with none while they review authentication.
Add a reporting address you control if you want aggregate reports.
Choose relaxed or strict alignment and an optional subdomain policy.
Copy the record, publish it in DNS, then verify it with the DMARC Checker.
This tool creates a draft. It does not automatically update your DNS records or verify every sending service.
| Policy | What it requests |
|---|---|
| p=none | No enforcement action is requested for messages that fail DMARC. |
| p=quarantine | Receivers are asked to treat failing messages as suspicious. |
| p=reject | Receivers are asked to reject failing messages. |
A p=none policy without a valid reporting address does not give you aggregate reporting.
The rua tag requests aggregate reports and the ruf tag requests failure reports. Use an address you control or a reporting service you trust, and do not invent one. Publishing a reporting address does not create a mailbox, and receivers decide whether to send reports.
Relaxed alignment lets the organizational domain match, while strict alignment requires an exact domain match. The adkim tag sets DKIM alignment and aspf sets SPF alignment. Choosing a mode does not prove that a message passes.
The sp tag requests a separate policy for subdomains. RFC 9989 also defines np for non-existent subdomains and t for testing. They are explained here for reference only, and this generator does not create them. Older tags such as pct, rf and ri are not promoted.
Create a TXT record.
Use _dmarc. Many providers add your domain automatically.
Paste the generated string. Update an existing record rather than adding a duplicate.
Run the DMARC Checker once DNS has updated.
Without rua you get no aggregate reporting visibility.
Competing records at _dmarc can prevent correct policy discovery.
Legitimate mail from an unaligned sender can be rejected.
Reports go to the address you publish, so check it carefully.
Publishing a record does not make your messages pass DMARC, and DMARC does not guarantee inbox delivery. Verify real sending sources before you enforce.
A tool that builds the DMARC TXT value for _dmarc.yourdomain.com from the policy, reporting address and alignment settings you choose, so you do not have to write the tag syntax by hand. It creates a draft and does not change your DNS.
Yes. You can generate a DMARC record without signing up.
As one TXT record at the _dmarc hostname of your domain, for example _dmarc.example.com. Many DNS providers add your domain automatically, so you enter only _dmarc in the host field.
Many domains start with p=none while they review authentication and reporting data. Move to quarantine or reject only when legitimate sending sources authenticate and align. Moving straight to reject can block legitimate mail.
No. Aggregate reports need a valid rua destination, and receivers must support and send them. Reporting is not instant.
The rua tag requests aggregate reports. The ruf tag requests message-specific failure reports, and support varies between receivers. This generator offers a rua address only.
They set DKIM and SPF alignment to relaxed or strict. Relaxed allows the organizational domain to match, and strict requires an exact domain match. Neither setting proves that a particular email will pass DMARC.
It requests a different policy for existing subdomains. If it is not set, inheritance follows DMARC policy-discovery rules.
RFC 9989 defines np for non-existent subdomains and t for policy testing. This generator does not create np or t tags, so add them by hand only if you understand them.
No. Competing DMARC policies at the same DNS name can prevent correct policy discovery. If a record already exists, review and update it instead of adding another.
No. It only creates the text. You publish the record yourself at your DNS provider, then verify it with the DMARC Checker.
No. DMARC is an authentication and policy mechanism. Inbox placement also depends on reputation, recipient filtering and other factors, and a correct record does not prove that your messages pass SPF, DKIM or DMARC.
Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.