How do you add a DMARC record in cPanel?
To add a DMARC record in cPanel, open Zone Editor, select Manage next to the domain, choose Add Record and add a TXT record named _dmarc with a value such as v=DMARC1; p=none; rua=mailto:reports@example.net. Save it. This only works if the cPanel server is authoritative for the domain's DNS, so check the nameservers first.
cPanel also offers a second route: the Email Deliverability interface can install a suggested DMARC record once SPF and DKIM are valid. This guide covers both routes, the nameserver check that decides whether either works, hosting-email pitfalls and the move to enforcement. DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail). For the protocol itself, start with the DMARC guide. If the zone lives on Cloudflare instead, follow how to add a DMARC record in Cloudflare DNS.
Version note: cPanel labels and menus differ between versions and themes. The steps here were checked against the cPanel & WHM documentation for version 136 (Zone Editor and WHM DNS Zone Manager) and versions 130 onwards (Email Deliverability), using the Jupiter theme's category layout. cPanel's newer Meridian theme groups tools into goal-based hubs, with DNS under the Websites hub, so the route to the same screens looks different there.
Key takeaways
- The record is a TXT record named
_dmarcin the domain's zone. In the Zone Editor, enter_dmarcand cPanel appends the domain. - Editing a zone in cPanel only changes live DNS when the domain's nameservers point at that server. If they point at a registrar or Cloudflare, add the record there instead.
- Set up DKIM and SPF in Email Deliverability first. cPanel's own documentation says DMARC requires valid SPF and DKIM records.
- The Zone Editor's DMARC form still offers Percentage, Report Format and Report Interval fields. RFC 9989 removed those tags, so leave them out.
- Start at
p=nonewith anruaaddress you control, then move top=quarantineandp=rejectwhen reports show every legitimate sender aligned.
Is the domain's DNS actually hosted on the cPanel server?
Check before you edit anything. cPanel keeps a zone for every domain on the account, whether or not the internet asks that server. If the nameservers point somewhere else, such as the registrar, Cloudflare or a client's own DNS provider, a _dmarc record added in cPanel is stored locally and served to nobody.
$ dig +short NS example.com
ns1.examplehost.net.
ns2.examplehost.net.
Compare the answer with the nameservers your hosting provider gave you for the account. On Windows, run Resolve-DnsName -Name example.com -Type NS. Our DNS lookup tool shows the same answer without a terminal.
cPanel's documentation is explicit about this. The Email Deliverability page says that to install a DKIM or SPF record correctly, "your server must be the authoritative nameserver", and that otherwise you must also have your nameserver provider update the authoritative zone. Its Repair option is unavailable when the system does not control the domain's DNS records.
| Nameservers point to | Where to add _dmarc |
Role of cPanel |
|---|---|---|
| The cPanel server or the host's DNS cluster | cPanel Zone Editor | Live DNS |
| Cloudflare | Cloudflare dashboard | Use cPanel only to read the suggested SPF and DKIM values |
| Registrar DNS | Registrar's DNS panel | Same as above |
| Azure DNS or another provider | That provider | Same as above |
This is common on inherited client sites, where DNS moved to Cloudflare years ago. Then the Cloudflare or Azure DNS guide applies, and cPanel's zone is a stale copy. For UK client domains whose nameservers point at 123-reg, follow how to add a DMARC record at 123-reg instead.
How do you add the DMARC record in the cPanel Zone Editor?
Open Zone Editor, select Manage next to the domain, then select Add Record (or the arrow beside it to pick a type). Choose TXT, enter _dmarc in the name field, paste the DMARC value into the record field and select Save Record. cPanel's documentation files the Zone Editor under its Domains section.
- Log in to cPanel for the account that holds the domain.
- Open Zone Editor.
- Select Manage next to
example.com. The Manage Zone screen lists the existing records with Name, TTL, Type and Record columns. - Use the filter box to search for
_dmarc. If a record already exists, edit it instead of adding another. - Select the arrow beside Add Record and choose TXT. A new row appears at the top of the table.
- Name:
_dmarc. - Record: the full DMARC string on one line.
- Select Save Record.
A first record in monitoring mode:
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.net
The Zone Editor documentation warns that "the Record text box will accept invalid data", so cPanel will not catch a typo. If you are unsure of the syntax, build the value with the DMARC record generator, or follow how to create a DMARC record step by step, which explains each tag.
What do you enter in the Name field: _dmarc or _dmarc.example.com.?
Enter _dmarc. cPanel appends the domain automatically: its documentation gives the example of entering user, which becomes user.example.com.. The documentation also shows a fully qualified name with a trailing dot, such as prefix.example.com., so _dmarc.example.com. with the final dot reaches the same place.
After saving, read the Name column. It should show _dmarc.example.com. once. cPanel's documentation does not describe what happens to a full name typed without the trailing dot, so if you see anything like _dmarc.example.com.example.com., delete that row and add it again with _dmarc.
For a subdomain in the same zone, enter _dmarc.marketing for marketing.example.com. More patterns are in DMARC record examples for common setups.
What TTL should you use?
Keep the zone's default unless you plan a change soon; cPanel's documentation gives no recommended value. A shorter TTL, for example 300 seconds, means a later policy change reaches resolvers faster.
Should you use the Zone Editor's DMARC record type?
You can, but check what it writes. Choosing DMARC from the Add Record menu creates a TXT record with a default DMARC value and a form with a Policy setting (None, Quarantine or Reject) and optional fields. Those fields include Percentage, Report Format and Report Interval, which correspond to tags that RFC 9989 removed.
The documentation says the Report Interval value defaults to 86400 seconds. RFC 9989 receivers ignore unknown tags, so leftovers are harmless but misleading. Fill in the policy and the aggregate report address, leave the other fields empty, then read the saved TXT value and remove any pct, rf or ri tag. Typing a plain TXT record avoids the question.
Can Email Deliverability add the DMARC record for you?
Yes, in current versions. cPanel's Email Deliverability interface checks DKIM, SPF, DMARC and reverse DNS (PTR) for each domain. Its DMARC section offers a Suggested DMARC (TXT) Record, which you can copy or, when the server is authoritative, install with Install the Suggested Record. It requires valid SPF and DKIM first.
The documentation does not show the suggested record's content, so it does not tell you which policy or report address it uses. View the suggestion before installing it. If it has no rua tag, or points reports at an address you do not control, add your own record in the Zone Editor instead, because a record without rua gives you no aggregate reports.
When the server is not authoritative, cPanel's instruction is to have the record added on the authoritative nameserver. Copy the value, then publish it at the real DNS host.
How do you enable DKIM and SPF in Email Deliverability first?
Open Email Deliverability, find the domain and select Manage. Fix DKIM and SPF there before you publish DMARC. cPanel's documentation states that the domain must have valid SPF and DKIM records for the DMARC record to be active, and the Repair button applies the recommended records when the server controls DNS.
What the interface does for each record, according to cPanel's documentation:
| Record | What cPanel offers | What to check |
|---|---|---|
| DKIM | Generate Local DKIM Key, view the record in full or split form | That the public key is published where the domain's DNS is actually hosted |
| SPF | A suggested record that includes the server's main IPv4 and IPv6 addresses, plus Customize for extra +a, +mx, IP blocks and +include items |
Every other sender is still listed; one v=spf1 record only |
| DMARC | Suggested record, copy or install | rua address and policy before installing |
| PTR | Shows the IP's current reverse DNS record and how to fix problems | Hostname resolves back to the sending IP |
By default, cPanel recommends ~all at the end of the SPF record and makes -all optional. Under DMARC, either works, because DMARC acts on SPF pass or fail, not on how strongly the SPF record states it. For a full walkthrough of the syntax, see how to create an SPF record.
If the domain's mail is hosted with Google Workspace or Microsoft 365 rather than on the cPanel server, cPanel's documentation points you to those providers' own DKIM and SPF instructions. Review any suggested SPF record before accepting a repair, so the provider's include: stays in the record.
What are the common hosting-email pitfalls?
Most DMARC failures on cPanel hosting come from mail the server sends on the site's behalf, not from the record itself. Contact forms and WordPress notifications go out through the server, and each must pass SPF or DKIM aligned with the From domain.
- PHP and WordPress mail. Mail sent with PHP's mail function leaves from the server's IP, which cPanel's SPF suggestion covers. DKIM is the weaker link: cPanel's documentation warns that DKIM may not verify PHP-sent mail when the DSO PHP handler is installed without MPM ITK. Send a test form submission to a mailbox you control and read the
Authentication-Resultsheader. - Envelope sender. SPF checks the Return-Path domain, not the From address. If a test message shows a Return-Path on the server's hostname rather than the client's domain, SPF cannot align, and DMARC depends on DKIM. Our email header analyzer shows both domains side by side.
- Server hostname and PTR. The PTR record maps the sending IP back to a hostname, and cPanel's documentation says it requires a matching A record. On shared hosting you rarely control it: the documentation tells you to contact the IP's owner, usually the host. A missing PTR hurts deliverability even when DMARC passes. See reverse DNS, PTR records and email authentication.
- Third-party senders. Newsletters, CRMs and ticketing tools that send as the domain need their own SPF include or, better, DKIM on the client's domain. cPanel's SPF Customize screen has an Add A New "+include" Item option for this.
How do you verify the DMARC record after publishing?
Query _dmarc and confirm exactly one DMARC record comes back with the intended value. Then return to Email Deliverability and check the domain's status. Under RFC 9989, if more than one DMARC record is returned, receivers discard them all, so a duplicate leaves the domain with no policy.
$ dig +short TXT _dmarc.example.com
"v=DMARC1; p=none; rua=mailto:dmarc-reports@example.net"
To skip resolver caches, ask one of the domain's own nameservers:
$ dig @ns1.examplehost.net +short TXT _dmarc.example.com
On Windows, use either of these:
Resolve-DnsName -Name _dmarc.example.com -Type TXT
nslookup -type=TXT _dmarc.example.com
The DMARC checker validates the syntax and flags duplicates. If a checker reports that no record exists even though you saved one, work through how to fix "no DMARC record found": the usual cause on cPanel is a zone the internet never queries.
Should the cPanel DMARC record include pct?
No. RFC 9989 replaced RFC 7489 in 2026 and removed pct, along with ri and rf. Older tutorials and the Zone Editor's DMARC form still show a percentage field, but a percentage ramp is historic. Publish each policy in full: p=none, then p=quarantine, then p=reject.
RFC 9989 adds np for non-existent subdomains and t for testing. If you want a cautious step, t=y asks receivers to apply the next lower policy:
v=DMARC1; p=quarantine; t=y; rua=mailto:dmarc-reports@example.net
Remove t=y once the level is confirmed. How to generate a compliant DMARC record lists the current tag set.
When do you move from p=none to quarantine and reject?
Move up when aggregate reports show every legitimate source passing SPF or DKIM with alignment: the cPanel server itself, the mailbox provider and each third-party sender. Then change p=none to p=quarantine, watch the reports again, and finally publish p=reject.
Edit the existing _dmarc row in the Zone Editor rather than adding a new one. A typical progression:
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.net
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.net
v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.net
The UK NCSC email security and anti-spoofing guidance follows the same principle: start at none, use reports to fix legitimate senders, then enforce. For subdomain policies and the sp and np tags, see DMARC for subdomains.
What should you check when the cPanel DMARC record does not work?
Start with the nameservers, then the record count, then the name. Most problems on cPanel come from editing a zone that is not live, adding a second record, or a name with the domain repeated. The table lists the usual symptoms and fixes.
| Symptom | Likely cause | Fix |
|---|---|---|
Record visible in Zone Editor, but dig returns nothing |
Nameservers point to another DNS host | Check dig NS and add the record at the real DNS host |
| Repair button unavailable in Email Deliverability | Server does not control the domain's DNS | Copy the suggested records and publish them at the authoritative host |
| Checker reports no valid policy | Two TXT records at _dmarc, one old and one new |
Delete one; RFC 9989 discards all when more than one returns |
| Name shows the domain twice | Full name entered without the trailing dot | Delete the row and re-add it with _dmarc |
| TXT missing from the Add Record menu | Host has not enabled the Zone Editor (AAAA, CAA, SRV, TXT) feature | Ask the hosting provider to enable it |
Saved record contains pct, ri or rf |
Values filled in through the DMARC form | Edit the TXT value and remove the historic tags |
| WordPress or form mail fails DMARC | Return-Path on the server hostname and no valid DKIM signature | Fix DKIM for the domain, or send through an authenticated mailbox |
| No aggregate reports arrive | No rua tag, or an external rua without authorisation |
Add rua; publish the receiver's _report._dmarc record |
How should MSPs handle DMARC for client sites on shared hosting?
Treat each cPanel account as a sending source, not just a DNS host. For every client, record where DNS is authoritative, which server sends the website's mail, and who controls the PTR. Then publish DMARC where the DNS actually lives and confirm in aggregate reports that the hosting server aligns.
- Map DNS first. Run
dig NSfor every client domain. Shared hosting accounts often hold a zone that stopped being authoritative when DNS moved elsewhere. - Use WHM where you run the server. Resellers and server owners can use WHM's DNS Zone Manager, which lists the server's domains and adds TXT or DMARC records with the same automatic domain appending. Hosting providers can enable or disable it for resellers.
- Templates do not fix existing zones. WHM's zone templates apply only when new zone files are created, according to cPanel's Edit Zone Templates page. Existing client domains still need their own record.
- Avoid zone resets. The Zone Editor's Reset DNS Zone action erases custom zone changes. cPanel says it tries to keep TXT entries, but note the
_dmarcvalue before anyone resets a zone. - Separate report destinations. If reports go to a mailbox on your own domain, that domain must publish an authorisation record such as
example.com._report._dmarc.example.netwith the valuev=DMARC1, as defined in RFC 9990, Section 4.
DMARC AI collects aggregate reports for every client domain in one multi-tenant view, so you can see whether a client's cPanel server, mailbox provider and third-party senders align before you move them to enforcement. More on running DMARC as a managed service is on DMARC for MSPs.
FAQ
How do I enable a DMARC policy in cPanel?
Publish a TXT record named _dmarc in the Zone Editor, or install the suggested record from Email Deliverability once SPF and DKIM are valid. Start with p=none and an rua address. The policy takes effect for receivers as soon as the record resolves from the domain's authoritative nameservers, which must be the cPanel server.
Does cPanel add a DMARC record automatically?
cPanel's documentation does not say that it adds one by default. Email Deliverability offers a suggested DMARC record that you install yourself, and the Zone Editor's DMARC record type fills in a default value when you choose it. Check the domain with dig or a DMARC checker rather than assuming a record exists.
Why does my cPanel DMARC record not show up in DNS lookups?
Usually because the domain's nameservers point to another provider, so the cPanel zone is not the live one. Run dig NS example.com. If the answer is Cloudflare, a registrar or another DNS host, add the _dmarc record there. Otherwise check for a duplicated domain in the record name.
Should I use ~all or -all in the cPanel SPF record?
cPanel recommends ~all by default and offers -all as an option. For DMARC the choice matters little, because DMARC evaluates whether SPF passed with alignment. What matters more is that every legitimate sender is listed and that the domain publishes only one v=spf1 record.
Next steps
Adding a DMARC record in cPanel takes a minute in the Zone Editor. The time goes into the checks around it: confirm the server is authoritative, fix DKIM and SPF in Email Deliverability, test the mail the website sends, and keep one _dmarc record. Then let aggregate reports decide when each client moves from p=none to p=reject.