# How to Create a DMARC Record and Roll It Out Safely

Canonical page: https://email-deliverability-desk.vercel.app/tools/dmarc-generator/

You have no DMARC policy yet and need a valid v=DMARC1 TXT value plus a safe way to tighten it.

Tool: [DMARC Generator](https://billionverify.com/dmarc-generator)

## What it checks

- Sets the policy to none, quarantine or reject
- Adds an optional separate subdomain policy
- Sets pct from 1 to 100, default 100
- Adds rua and ruf mailto addresses when given
- Sets SPF and DKIM alignment to relaxed or strict
- Shows the _dmarc host name and the TXT type

A DMARC record is short, but one wrong tag can send real mail to spam or drop it. This page explains how to create a DMARC record, what the generator puts in it, and a rollout order that does not surprise you.

**Key facts:**

- A DMARC record is a single TXT value at `_dmarc.yourdomain` that begins with `v=DMARC1` (RFC 7489).
- A domain must publish only one DMARC record, and receivers do not apply DMARC when they find several (RFC 7489).
- Relaxed alignment is the default, and it lets a subdomain of the From domain align with it (RFC 7489).
- Per the BillionVerify DMARC Generator, it builds the value in the browser and always writes `pct`, `adkim` and `aspf` into the record.
- Per the BillionVerify DMARC Generator, the policy starts at `none` and alignment starts at relaxed.

## How to create a DMARC record

Do this first. Confirm that SPF and DKIM already pass for every service that sends as your domain. DMARC adds nothing until one of them passes and aligns.

Then fill in the generator:

1. Enter your domain. A blank field falls back to `example.com`, so type your own.
2. Leave the policy at `none` for the first run.
3. Add a `rua` address that can receive aggregate reports. Without one, you get no data.
4. Keep alignment relaxed unless you have a reason to go strict.
5. Generate, then copy the record.

A first record looks like this:

`v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com; pct=100; adkim=r; aspf=r;`

## What each setting does

### Policy and subdomain policy

`p=none` asks for monitoring only. `quarantine` asks receivers to treat failures as suspicious. `reject` asks them to refuse the mail. The optional `sp=` tag sets a different policy for subdomains. Left alone, subdomains inherit `p=`.

### Percentage

The slider limits how much failing mail the policy covers. Use a low value when you move to `quarantine` or `reject`, then raise it.

### Reports and alignment

`rua` receives aggregate reports and `ruf` receives failure reports. Treat `ruf` as optional, because many receivers do not send it. Relaxed alignment accepts subdomains of your domain, and strict demands an exact match. A report address on another domain needs a matching authorization record on that domain (RFC 7489).

## How to publish and roll it out

Add the TXT record at the host the tool shows, which is `_dmarc.` followed by your domain. Make sure no older DMARC record exists.

Then move in stages:

1. Stay at `p=none` and read the reports until every real sender passes.
2. Move to `quarantine` with a low `pct`.
3. Raise `pct` while the reports stay clean.
4. Move to `reject` when you are confident.

Publish each change by replacing the old value, so generate the record again with the new settings.

## How to verify the record

After DNS updates, run the domain through a DMARC checker. The policy, subdomain policy and pct should match what you set. If the record prints without policy lines, the `p=` tag is missing.

Authentication does not clean a list. A record that passes everything still bounces on dead addresses. Before a large send, try [BillionVerify's Email Checker](https://billionverify.com/email-checker) on a few addresses. You get 20 free full checks per IP every 24 hours, no sign-up.

For a wider test of your setup, send a message through a full deliverability test, and use [billionverify.com](https://billionverify.com/email-verifier) when a single recipient keeps failing.
