Free DMARC Record Generator
Anyone can forge email from your domain until you publish DMARC. This builds the record that shuts that down.
You decide how mailbox providers handle mail that fails SPF or DKIM alignment for your domain, choosing to monitor it, quarantine it, or reject it, and where they send aggregate reports. Generate the exact record below, then paste it into your DNS.
Your DMARC Record
Publish this as a TXT record at host _dmarc on your DNS provider. It replaces whatever is currently there.
DNS provider instructions
How It Works
Enter your domain
Type the sending domain you want to protect. We generate a valid DMARC record tailored to your setup. No signup required.
Pick your policy
Choose how strict to be (monitor, quarantine, or reject) and where to send aggregate reports. The tool composes the exact TXT record for you.
Add the TXT record to DNS
Copy the generated record and add it at host _dmarc in your DNS provider. Most receivers see it within an hour.
What is a DMARC record?
A DMARC record is a DNS TXT record that helps protect a domain from email spoofing by telling receiving mail servers how to handle mail that fails SPF or DKIM authentication.
Published at _dmarc.yourdomain.com, the record sets a policy (p=none to monitor, p=quarantine, or p=reject) and a reporting address (rua) where receivers send daily summaries of who’s sending as your domain. Because it builds on SPF and DKIM, the usual rollout runs Monitor → Quarantine → Reject, tightening enforcement only once your legitimate mail passes alignment. InboxAlly’s free DMARC Record Generator builds a valid record from your inputs, looks up your current one, and verifies external report destinations per RFC 7489 §7.1.
See How the DMARC Generator Works
Why Publish a DMARC Record?
Stop domain spoofing
DMARC tells receivers to reject or quarantine unauthenticated mail claiming to be from your domain — the strongest defense against phishing impersonation.
Meet sender requirements
Gmail and Yahoo require a published DMARC record (at minimum p=none) for bulk senders. A correctly formed record keeps you compliant.
Get visibility into who sends as you
Aggregate (rua) reports show every IP and ESP sending mail claiming to be from your domain — including the ones you didn’t know about.
Strengthen overall deliverability
A passing DMARC alignment improves how mailbox providers trust your mail, contributing to better inbox placement over time.
Understanding Your DMARC Policy
Receivers take no enforcement action on failing mail but still send you aggregate reports. Safe starting point while you audit who sends as your domain.
Mail that fails alignment lands in the recipient's spam folder. Use once your legitimate senders are passing reliably.
Failing mail is bounced outright. The end state, required by Gmail and Yahoo for high-volume senders and the strongest defense against domain spoofing.
DMARC Record Generator FAQ
Do I need SPF and DKIM before publishing DMARC?
Yes. DMARC builds on SPF and DKIM — it tells receivers what to do when a message fails alignment with either. Publish SPF and DKIM first, verify both are passing for your real mail streams, then turn on DMARC starting with p=none.
What policy mode should I start with?
Start with p=none (monitor only). It enables aggregate reporting without enforcement, so you can see who is sending as your domain before any mail gets blocked. Move to p=quarantine, then p=reject, once your legitimate senders are passing reliably.
Where do I add the generated record?
As a DNS TXT record at the host name _dmarc on your sending domain (for example _dmarc.example.com). Most DNS providers ask only for the host name and the value — the generator gives you exactly the value to paste.
How long does it take for DMARC to take effect?
DNS propagation typically completes within an hour, though some receivers cache for up to 24 hours. Aggregate reports (rua) usually start arriving the next day from receivers that send them.
What is the difference between rua and ruf addresses?
rua receives aggregate XML reports — high-level statistics about authentication results. ruf receives forensic reports — copies of failing messages. Most senders only configure rua; ruf can produce sensitive content and is supported by fewer receivers.
Does publishing DMARC affect my deliverability?
A correctly aligned DMARC record helps deliverability by signaling that you take authentication seriously. A misconfigured record can hurt it — which is why p=none is the safe starting policy until you confirm alignment.
DMARC Stops Spoofing.
InboxAlly Earns the Inbox.
Publishing a DMARC record protects your domain from impersonation. Earning consistent inbox placement is a different problem. InboxAlly teaches mailbox providers to put your real mail where it belongs.