DMARC generator

Build a DMARC record from explicit options, starting with a monitoring policy, with each tag explained.

What receivers do with messages that fail DMARC.

Comma-separated addresses. External domains must authorise your domain.

Optional; few providers send them and they may contain message content.

Leave empty for 100.

Record to publish

Publish as a TXT record on _dmarc.example.com

v=DMARC1; p=none
  • Info: Policy: none (monitoring)Receivers take no action on failures but send reports. Good starting point; move on once reports look clean.
  • Warning: No aggregate report addressWithout rua= you receive no feedback about who sends on behalf of the domain.
  • v=DMARC1DMARC version
  • p=nonePolicy for the domain: none

Typical path: p=none with reports, review sources for a few weeks, then p=quarantine, then p=reject. Reject is not a universal fix.

Scope and limits

  • Starts at p=none on purpose: enforcement should follow once reports show every legitimate source aligned.
  • Does not receive reports or host rua/ruf mailboxes.

Related tools and resources

Read the DMARC policy of a domain, resolving inheritance from the organizational domain, with every tag explained.

Domain and authentication

Open a DMARC aggregate report (XML, .gz or .zip): reporter, policy, volumes by source IP and the SPF/DKIM results each row declares.

Messages, headers and errors

Compose an SPF record from the sources you declare: IPs, networks, includes, a, mx and the final policy, with each part explained.

Domain and authentication
Mailiqo

Set up your sending domain in Mailiqo

Mailiqo verifies your domain from the panel and guides you through the SPF, DKIM and DMARC records you need to send under your own identity. Free plan, no card required.

Create a free account