To set up DMARC on Namecheap, go to Domain List > Manage > Advanced DNS, click Add New Record, choose TXT Record, enter _dmarc as the Host and v=DMARC1; p=none; rua=mailto:[email protected] as the Value, then click Save all changes. Start with p=none, read the reports, and only then move to quarantine and reject.
DMARC tells mailbox providers what to do with email that claims to come from your domain but can't prove it, and sends you reports on who is sending as you.
Last verified: November 13, 2026, against Namecheap's official knowledge base.
Before you start: SPF and DKIM
DMARC passes only when SPF or DKIM passes for your own domain. Set both up first.
SPF
One TXT record on @ starting with v=spf1, covering every service that sends as you. For Namecheap Private Email: v=spf1 include:spf.privateemail.com ~all. See our guide on adding an SPF record on Namecheap.
DKIM for Private Email
- In your Namecheap account, open the Private Email menu.
- Click Manage next to your domain.
- Click Generate under DKIM. Namecheap confirms with "DKIM has been generated."
On BasicDNS, Namecheap says the DKIM TXT record should be configured automatically. Its host is privateemail._domainkey (default._domainkey for subscriptions bought before June 2, 2026). On other DNS, copy the record to your DNS provider.
If you use Google Workspace or Microsoft 365 instead, turn on DKIM in their admin console and publish the key they give you.
Step 1: pick an address for reports
Mailbox providers send daily XML reports to the rua address. Use a dedicated mailbox on your own domain, such as [email protected]. An address on another domain needs an extra authorization record on that domain.
Step 2: add the DMARC record
- Go to Domain List and click Manage next to your domain.
- Open the Advanced DNS tab and click Add New Record.
- Type: TXT Record. Namecheap asks for TXT even for SPF, DKIM and DMARC records.
- Host:
_dmarc. Do not include your domain name. Value:
v=DMARC1; p=none; rua=mailto:[email protected]- Leave the TTL at its default and click Save all changes.
Namecheap says new host records normally take effect within 30 minutes. These steps apply to BasicDNS, PremiumDNS and FreeDNS; on Namecheap hosting DNS, add the record in cPanel.
Step 3: read reports, then tighten the policy
p=nonefor at least one to two weeks. Open the reports and list every service sending as you. Fix any that fail SPF and DKIM.p=quarantineonce every legitimate sender passes: failing mail goes to spam.p=rejectonce reports have stayed clean for several weeks: failing mail is refused.
Namecheap's knowledge base shows v=DMARC1;p=reject;sp=quarantine;pct=100 as an example value. That is an end state, not a starting point. Published on day one, it can block your own invoices or newsletters if one sender was forgotten.
Step 4: check it works
nslookup -type=TXT _dmarc.yourdomain.comYou should see one line starting with v=DMARC1. Our free DMARC checker explains each tag. Then send an email to a Gmail address, open it and choose Show original: SPF, DKIM and DMARC should all show PASS.
Known pitfalls
- Two DMARC records: receivers ignore both. Edit the existing
_dmarcrecord instead of adding one. _dmarc.yourdomain.comin the Host field: it becomes_dmarc.yourdomain.com.yourdomain.com. Enter only_dmarc.- Missing
mailto:before the report address: the prefix is required. - SPF over 10 DNS lookups: SPF then fails with an error, and DMARC depends on DKIM alone.
- Relying on
pct: the updated DMARC standard (RFC 9989, May 2026) removed that tag. Rely on your reports instead.
Frequently asked questions
A scanner says "DMARC policy not enabled." What should I do?
It means you have no DMARC record or a p=none policy. Publish p=none with reports first, check that your senders pass, then move to quarantine as in Step 3.
Do I need a separate DMARC record for subdomains?
No. Without an sp= tag, your main policy also covers subdomains.
Verify it's fixed. AttackScout reads your DMARC, SPF and public DKIM records, spots duplicates or a policy that's too weak, and tells you when it's safe to tighten it. Free, no account needed. Verify it's fixed
Technical details
Exact configuration. A TXT record on the _dmarc name of your domain:
_dmarc.your-domain.com TXT "v=DMARC1; p=none; rua=mailto:[email protected]"Why. DMARC (RFC 7489) tells the receiving server what to do with an email that claims to come from your domain but passes neither SPF nor DKIM with that same domain name (alignment). p=none observes without blocking; p=quarantine sends to spam; p=reject refuses. rua receives the aggregate reports that show who sends in your name: tighten the policy only after reading them.
To check it yourself. Exactly one line must start with v=DMARC1:
dig +short TXT _dmarc.your-domain.comReference: https://www.rfc-editor.org/rfc/rfc7489
Sources
Accessed November 13, 2026.
- Namecheap, How do I add TXT/SPF/DKIM/DMARC records for my domain?: https://www.namecheap.com/support/knowledgebase/article.aspx/317/2237/how-do-i-add-txtspfdkimdmarc-records-for-my-domain/
- Namecheap, How to set up a DKIM record for Private Email: https://www.namecheap.com/support/knowledgebase/article.aspx/10383/2176/how-to-set-up-a-dkim-record-for-private-email/
- Namecheap, How to set up Namecheap Private Email DNS records: https://www.namecheap.com/support/knowledgebase/article.aspx/1338/2176/how-to-set-up-namecheap-private-email-dns-records/
- IETF, RFC 9989 (DMARC, May 2026): https://www.rfc-editor.org/info/rfc9989
- Google Workspace, Recommended DMARC rollout: https://knowledge.workspace.google.com/admin/security/recommended-dmarc-rollout
- Google, Email sender guidelines: https://support.google.com/mail/answer/81126?hl=en