ETEvoraTools
DNS & Email Security

DMARC Record Generator

DMARC Record Generator creates a minimal v=DMARC1 record using a selected p policy and optional rua mailto address. It does not validate the domain, SPF or DKIM alignment, external report authorization, mailbox capacity, XML report processing, or DNS publication. Moving directly to quarantine or reject can disrupt legitimate mail.

Runs locally — files stay on your device
Quick answer

What does p=none do?

It requests monitoring without asking receivers to quarantine or reject failing mail, though receiver behavior and local policy can still vary.

DMARC combines authentication alignment with a domain policy

DMARC evaluates whether SPF or DKIM passes with alignment to the visible From domain, then publishes a requested policy and optional reporting destinations.

How it works

Choose none, quarantine, or reject and optionally enter an aggregate-report email address. The tool emits a minimal semicolon-delimited record beginning with v=DMARC1.

Key concepts

Alignment matters

A raw SPF or DKIM pass is insufficient when its authenticated domain does not align with the visible From domain.

Reporting creates operations work

Aggregate XML reports require secure receipt, storage, parsing, and monitoring.

When to use it

  • Draft a monitoring policy.
  • Create a minimal aggregate reporting record.
  • Compare DMARC policy values before expert review.

When not to use it

  • Do not enforce reject before validating all mail streams.
  • Do not expect DMARC to configure DKIM or SPF.
  • Do not publish reporting addresses without operational and privacy planning.

Worked examples

Monitoring draft

Input
Policy none; reports dmarc@example.com
Expected output
v=DMARC1; p=none; rua=mailto:dmarc@example.com;

The mailbox is inserted without external authorization checks.

Quarantine draft

Input
Policy quarantine; no email
Expected output
v=DMARC1; p=quarantine;

No rua tag is added.

Reject draft

Input
Policy reject
Expected output
v=DMARC1; p=reject;

This strict request should follow monitored rollout.

Common mistakes

Starting at reject

Uncatalogued legitimate mail can be affected. Correction: Monitor, remediate alignment, and roll out deliberately.

Assuming DMARC creates authentication

SPF and DKIM must be configured separately. Correction: Verify aligned authentication first.

Ignoring report handling

Reports can be numerous and contain operational metadata. Correction: Use a secured, monitored mailbox and processor.

Best practices

  • Begin with visibility and sender inventory.
  • Verify SPF and DKIM alignment for each stream.
  • Plan report retention, privacy, and gradual enforcement.

Related operations and differences

CIDR to Range

Choose CIDR to Range when you need to calculate an IPv4 network and broadcast address.; use DMARC Record Generator specifically for dmarc.

cURL Command Builder

Choose cURL Command Builder when you need to build a basic cURL command from manual fields.; use DMARC Record Generator specifically for dmarc.

Fetch Request Builder

Choose Fetch Request Builder when you need to build a browser fetch request snippet.; use DMARC Record Generator specifically for dmarc.

HTTP Header Formatter

Choose HTTP Header Formatter when you need to normalize spacing in pasted HTTP headers.; use DMARC Record Generator specifically for dmarc.

IP Address Validator

Choose IP Address Validator when you need to validate IPv4 or basic IPv6 syntax.; use DMARC Record Generator specifically for dmarc.

IPv6 Compressor

Choose IPv6 Compressor when you need to compress zero groups in an IPv6 address.; use DMARC Record Generator specifically for dmarc.

Limitations and privacy

  • Generates only p and optional rua.
  • No pct, subdomain policy, alignment mode, forensic reporting, DNS, or external-destination validation.
  • Does not publish or test the record.

The entered network data is processed locally in this browser.

Frequently asked questions

Does DMARC replace SPF and DKIM?

No.

Does this publish the TXT record?

No.

What is rua?

An aggregate report destination.

Should every new domain start with reject?

No; enforcement should follow validated monitoring and rollout.

References