If you’ve already set up DKIM and SPF records for your domain in cPanel, we recommend adding a DMARC policy as well.
DMARC, which stands for Domain-based Message Authentication, Reporting and Conformance, is a DNS record that adds another layer of protection for your domain.
It tells receiving mail servers what to do when an email appears to come from your domain but does not pass authentication checks, and it can also provide reports showing how your domain is being used for email.
This helps reduce the risk of:
Before adding DMARC, make sure your SPF and DKIM records are already in place. For more information, please see:

NOTE: If you're using external email servers instead of cPanel for sending your domain emails, you'll need to manually adjust the following cPanel Suggested DMARC policy. Please consult your IT Support to do this.

NOTE: If you've registered your domain with a third party, or using external name servers, you'll need to add the DMARC with the SPF/DKIM records onto the DNS platform you use.





We now need to copy the information from the previous cPanel page, into the TXT record page within the Zen Customer Portal with your current DKIM and SPF records using the blank space provided.
Note: This section is intended for email administrators and advanced cPanel users. It is provided as general guidance only.
By default, cPanel publishes the following DMARC record:
v=DMARC1; p=none;
This is a monitoring-only policy that allows email providers to collect DMARC reporting data without quarantining or rejecting messages that fail authentication checks.
DMARC supports a range of tags that can be used to customise how email authentication is monitored and enforced. Commonly used tags include:
p – Policy for the primary domainsp – Policy for subdomainspct – Percentage of messages the policy applies torua – Address for aggregate DMARC reportsruf – Address for forensic (failure) reportsadkim – DKIM alignment modeaspf – SPF alignment modeThe p and sp tags support three policy options:
none – Monitor email traffic and reporting only.quarantine – Request that receiving mail servers treat failing messages as suspicious (for example, by placing them in a spam or junk folder).reject – Request that receiving mail servers reject messages that fail DMARC checks.The pct tag can be used to apply a policy to only a percentage of failing messages, allowing a gradual rollout before full enforcement.
A recommended deployment approach is to:
p=none.p=quarantine once legitimate email is consistently passing authentication checks.p=reject when you are confident that all authorised email sources are correctly aligned.This phased approach helps minimise the risk of legitimate email being affected while strengthening protection against email spoofing and phishing.
Our support team can assist with cPanel administration and DNS-related tasks. However, the configuration and management of DMARC policies remain the responsibility of the domain owner.
Before implementing or changing a DMARC policy, you should ensure that you understand how your domain sends email and how a policy change may affect email delivery. If you are unsure which policy is appropriate for your environment, we recommend consulting your internal IT team or email administrator.
While we can provide general guidance, we are unable to design, select, or manage a DMARC policy on your behalf.
If encountering problems entering any records, feel free to contact our Web Hosting team.