DMARC Record Generator Email

A DMARC record generator builds the TXT record that tells receiving mail servers what to do with messages that fail authentication for a domain, and where to send reports about them. Choose a policy, add a report address, and copy the record to the _dmarc host of the domain.

Used for the host name and the check links below. The record is built in your browser.

Policy for mail that fails DMARC p
Reports

Daily XML summaries of which servers sent mail as the domain and whether it passed. Use a dedicated mailbox or a report-processing service.

Subdomains and rollout
Alignment, failure report options and legacy tags
When to send a failure report fo

pct and ri were removed from DMARC by RFC 9989. Leave them at 100 and 86400 unless you need them for receivers that still follow RFC 7489.

DMARC record to publish

Type
TXT
Host
@
Value

    How to use the DMARC generator

    1. Pick the policy. A domain publishing DMARC for the first time should start with none, which changes nothing about delivery.
    2. Add an aggregate report address. The reports are the reason to publish p=none: they list every server that sent mail as the domain and whether it passed.
    3. Leave the rest at the defaults unless you have a reason to change them. The generator omits any tag that is at its default value, so the record stays short.
    4. Publish the value as a TXT record with the host _dmarc. If a record already exists there, replace it.
    5. Verify the live record with the DMARC Lookup.

    DMARC tags

    The current DMARC specification is RFC 9989, published in May 2026, which replaced RFC 7489. Records written for the old specification still work: the version tag is unchanged and receivers ignore tags they do not process.

    TagMeaningDefault
    v=DMARC1Version. Required, and must be the first tag.—
    pPolicy for mail that fails DMARC: none, quarantine or reject.—
    spPolicy for subdomains that have no DMARC record of their own.Same as p
    npPolicy for subdomains that do not exist in DNS. Added by RFC 9989.Same as sp
    tTest mode. t=y asks receivers not to apply the policy yet. Added by RFC 9989.n
    ruaAddresses for aggregate reports, as mailto: URIs separated by commas.None
    rufAddresses for per-message failure reports. Few large providers send them.None
    adkimDKIM alignment: r (relaxed) accepts a signing domain that shares the organizational domain with the From address; s (strict) needs an exact match.r
    aspfSPF alignment, with the same two values, applied to the envelope sender domain.r
    foWhich failures trigger a failure report: 0, 1, d or s. Only used with ruf.0
    psdpsd=n declares the domain to be the organizational domain, which ends the receiver's search for a policy record there. Added by RFC 9989.u
    pctShare of failing mail the policy applied to. Removed by RFC 9989; receivers that follow it ignore the tag.100
    riRequested interval between aggregate reports, in seconds. No longer part of the specification.86400

    Rolling out a policy: none, quarantine, reject

    Moving straight to p=reject blocks any legitimate sender that has not been set up correctly. The usual order is:

    1. p=none with rua. Collect reports for a few weeks. Every source that sends real mail for the domain should show an aligned SPF or DKIM pass. Fix the ones that do not: add them to the SPF record, turn on DKIM signing with the domain's own key, or move them to a subdomain.
    2. p=quarantine. Failing mail goes to the spam folder, where a mistake is still recoverable. Adding t=y first publishes the intent without asking receivers to act on it. Older guides stage this step with pct; receivers that follow RFC 9989 no longer process that tag.
    3. p=reject. Failing mail is refused. Keep the report address in place so that a new sending service shows up before its mail is lost.

    Google, Yahoo and Microsoft require domains that send bulk mail to their users to publish a DMARC record, with p=none as the minimum. The guide to moving from p=none to p=reject walks through the rollout in detail.

    What has to pass

    DMARC does not authenticate mail itself. A message passes when at least one of two checks passes and is aligned with the domain in the From header:

    • SPF: the sending server is authorized by the SPF record of the envelope sender domain, and that domain matches the From domain. Build the record with the SPF record generator.
    • DKIM: the message carries a valid signature whose d= domain matches the From domain. Check which keys a domain publishes with the DKIM Lookup.

    One aligned pass is enough. Forwarding usually breaks SPF and leaves DKIM intact, which is why signing with DKIM matters before a domain moves to enforcement.

    Where the record goes

    Publish the value as a TXT record named _dmarc under the domain, so the full name is _dmarc.example.com. A name can hold only one DMARC record; when receivers find two they discard both. A subdomain that sends mail can have its own record at _dmarc.sub.example.com, and otherwise falls under the sp policy of the organizational domain.

    If reports are sent to an address on a different domain, that domain has to agree to receive them by publishing a TXT record at example.com._report._dmarc.its-domain containing v=DMARC1. Report-processing services do this for their customers. The generator flags report addresses that need it.

    Frequently asked questions

    What does a DMARC record generator produce?

    A single TXT value such as v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com, to be published at the host _dmarc of the domain. The generator assembles it from the policy, report addresses and options you choose and leaves out tags that are at their defaults.

    Which DMARC policy should I start with?

    p=none together with a rua address. It does not affect delivery and produces the reports that show which servers send mail as the domain. Move to quarantine and then reject once every legitimate source passes.

    Do both SPF and DKIM have to pass for DMARC?

    No. One of them has to pass and be aligned with the domain in the From header. In practice both should be set up, because forwarding often breaks SPF and DKIM then carries the result.

    What is the difference between rua and ruf?

    rua receives aggregate reports: daily XML summaries of sending sources and pass or fail counts, sent by most large receivers. ruf receives failure reports about individual messages, which most large mailbox providers do not send for privacy reasons.

    Is the pct tag still used?

    RFC 9989 removed pct from DMARC in May 2026. A record that contains it is still valid, but receivers that follow the new specification ignore the tag and apply the policy to all failing mail. The replacement for a staged rollout is test mode, t=y.

    Does a DMARC record cover subdomains?

    Yes. A subdomain without its own DMARC record falls under the record of the organizational domain, using the sp policy if one is set and p otherwise. Subdomains that do not exist in DNS can be given a separate policy with np.

    Last updated: