Creating a DMARC record protects your brand by ensuring only authenticated emails are delivered. Below is a quick‑fire Q&A that walks you through the entire process, from understanding DMARC basics to publishing the record in your DNS.
It tells receiving mail servers how to handle messages that fail authentication checks. By publishing a TXT record, you can instruct servers to reject, quarantine, or simply monitor suspicious mail. This reduces phishing, spoofing, and improves your sender reputation.
DMARC is stored as a TXT record under the sub‑domain _dmarc.yourdomain.com
. The record contains tag‑value pairs that define version, policy, reporting addresses, and alignment settings.
The most common tags are v=DMARC1
(version), p=
(policy – none, quarantine, reject), rua=
(aggregate report address) and ruf=
(forensic report address). Optional tags control alignment (aspf
, adkim
) and percentage of mail to which the policy applies (pct
).
Use Palisade’s free DMARC record generator. Select a policy, add reporting emails, choose alignment modes, and the tool builds the exact TXT string for you.
_dmarc
(the provider will append your domain automatically).Run Palisade’s DMARC lookup tool. It queries your DNS and shows the exact record that receivers see.
Begin with p=none
(monitoring mode). This collects reports without affecting delivery, letting you fine‑tune alignment and identify legitimate sources before moving to quarantine
or reject
.
DMARC builds on SPF and DKIM. Both must be correctly configured for DMARC to pass. Use Palisade’s SPF checker and DKIM validator to confirm they are working.
Yes. After DMARC is enforced, you can publish a BIMI record that points to your brand’s SVG logo. Palisade’s BIMI tool helps you create and test the record.
Double‑check the host name (_dmarc.yourdomain.com
) and ensure the TXT value is correctly quoted. Use Palisade’s lookup tool to see exactly what is published.
Configure the rua
tag with an email address you control. Palisade can parse incoming XML reports and display them on a dashboard, highlighting sources that fail authentication.
Review the reports, tighten SPF/DKIM alignment (switch from relaxed to strict), and gradually move the policy from none
→ quarantine
→ reject
. This phased approach prevents legitimate mail from being blocked.
By proving to inbox providers that you actively protect your domain, they are more likely to trust your mail, reducing spam folder placement and boosting sender reputation.
Palisade offers live chat support and a knowledge base. Sign in to your dashboard, open a ticket, or schedule a quick call with a deliverability specialist.
p=none
to collect reports without affecting delivery._dmarc.yourdomain.com
and verify with the lookup tool.rua
tag and Palisade’s dashboard.quarantine
then reject
once you’re confident.rua
tag.sp=
tag to define a sub‑domain policy, or create separate DMARC records for each sub‑domain.Ready to secure your email? Check your DMARC security score now and let Palisade guide you through the setup.