Choose how recipients should handle messages that fail DMARC and where to send reports. The generator builds a DNS TXT record in your browser. If you are setting up DMARC for the first time, start with monitoring: p=none.
Several are fine, comma-separated. Gmail, Microsoft and others will send daily summaries here. If the address is on another domain, that domain must allow the reports with a record of its own.
A number from 1 to 100. 100 applies the policy to all mail; less applies it to part of it, for a transition.
_dmarcTXTWith p=none, you ask recipients to send reports to the rua= address without rejecting messages under the DMARC policy. Collect data over a normal business cycle, including newsletters, CRM mail and occasional notifications.
Once all your mail sources pass DMARC, you can choose p=quarantine to ask recipients to send failing messages to spam. DMARC requires either SPF or DKIM to pass and align with the From domain.
p=reject asks recipients to reject messages that fail DMARC. Switch to this policy once reports show it will not affect your legitimate mail. The receiving server makes the final decision.
Where to add a DMARC record and how to set up report addresses.
In the domain’s DNS, as a TXT record named _dmarc: most panels want exactly that, without the domain, and where the full name is required it’s _dmarc.example.com. The value is the line from the generator. There must be one record, so replace any existing one.
Yes, but that domain has to allow it with a record of its own: for example.com reports to a mailbox at example.net, example.net needs a TXT record example.com._report._dmarc.example.net with the value v=DMARC1. Without it, recipients won’t send reports to the other domain. Report analysis services usually have this set up already.
Usually not. The ruf= tag asks for a report on every failing message, but Gmail, Microsoft and most large providers don’t send those for privacy reasons. The aggregate rua= reports are enough to get things set up, which is why the generator doesn’t offer ruf.
MX, SPF, DKIM, DMARC and blacklists in one go, scored out of nine.
OpenCheck an SPF record for errors, the DNS lookup limit and sender rules.
OpenFind a DKIM key in DNS and check its length and status.
OpenWhether there is a record, which policy it sets and where reports go.
OpenThe domain’s mail servers, their addresses, reverse DNS and encryption.
OpenCheck an IPv4 address or a domain’s mail server IPs against blacklists.
OpenChoose your mail senders to create an SPF record for DNS.
OpenOn our hosting, mailboxes on your domain are part of the plan, and mail records are set up in the Plesk panel.
Host MX, SPF, DKIM and DMARC on our name servers: you edit records yourself at any time, the domain can stay with any registrar and mail with any provider.