DMARC record generator
Pick a policy, add a reporting address and copy the record. New domain? Start with p=none and tighten it once your reports are clean.
Monitor only. Nothing is blocked. Start here on a new domain.
Daily summaries of who sent as your domain. Strongly recommended.
v=DMARC1; p=none
New domain? Publish p=none first with a rua address. After a couple of weeks of reports showing only your own senders passing, move to quarantine, then reject. Jumping straight to reject can block your own mail if SPF or DKIM is not fully set up.
Relaxed alignment lets mail signed by a subdomain count for the main domain. It is the right default for most senders.
Frostmailer Azure tenants come with the .com domain included and authentication configured before handover. €30 per tenant.
Related tools
SPF record generator
Build an SPF record for Microsoft 365, Google Workspace or custom senders, with a live lookup count.
MXMX lookup
See a domain's MX records in priority order and which mail provider runs them.
NSNameserver lookup
Find a domain's nameservers and the DNS host behind them, so you know where to edit records.
Questions
Where does the DMARC record go?
A TXT record at _dmarc on your domain, for example _dmarc.example.com.
Why start with p=none?
p=none only monitors. It lets you see who sends as your domain before you start asking receivers to junk or reject mail that fails.
What is rua?
The address that receives daily aggregate reports. Without it DMARC still works, but you get no visibility.
Do I need ruf failure reports?
Rarely. Few receivers send them, and they can contain message content. Most senders leave ruf out.