18 Nov 2026 · 6 min read · EN
SPF, DKIM & DMARC: a practical deliverability checklist for cPanel domains (2026)
A practical checklist for cPanel-hosted domains: publish a tight SPF, install DKIM, add a staged DMARC policy, and set reverse DNS (PTR). Includes commands to test and what to watch for.
By Tim Gocelerus
Problem: Your mail is being marked as spam or rejected because SPF/DKIM/DMARC or reverse DNS aren't aligned. Fixing those four items (SPF, DKIM, DMARC, PTR) and testing them will dramatically reduce authentication failures.
How the three fit together
DMARC requires that an incoming message passes either SPF (with SPF alignment) or DKIM (with DKIM alignment). If neither passes and aligns, DMARC fails and receivers apply the domain owner's DMARC policy.
- SPF validates the MAIL FROM (envelope/return-path) IP against the sending domain's SPF TXT record.
- DKIM provides a cryptographic signature tied to a signing domain (the d= tag in the signature).
- DMARC checks that the visible From: header aligns with either the SPF-authenticated envelope or the DKIM signing domain and publishes a policy and reporting addresses.
(If you want the formal references, see the industry sender best practices and SPF guidance listed in the sources.)
Quick checklist (high level)
- Publish a narrow SPF for the envelope domain that explicitly lists sending IPs/hosts and stays under the 10-DNS-lookup limit.
- Enable DKIM signing; if you manage DNS, publish the DKIM public key TXT for the selector cPanel/WHM suggests.
- Publish a DMARC TXT at _dmarc; start with policy=none and collect reports before enforcing.
- Ensure reverse DNS (PTR) for the sending IP points to a hostname that resolves to the same IP (FCrDNS) and matches your mail HELO/EHLO.
- Test with live headers and DNS lookups; iterate until SPF or DKIM+alignment passes and DMARC reports show success.
1) SPF — publish a tight record and respect the lookup limit
- Gather every place that sends mail for your envelope/return-path domain: your server IPs, any mail relays, newsletter services, transactional providers.
- Use cPanel "Zone Editor" (or WHM: Home » DNS Functions » Edit DNS Zone) to add or edit the TXT record for the sending domain.
- Prefer explicit ip4:/ip6: mechanisms where possible and remove includes for providers you no longer use. Avoid +all or other permissive qualifiers.
Example SPF TXT (replace with your IPs/providers):
example.com. TXT "v=spf1 ip4:203.0.113.10 include:spf.examplemail.com -all"
- Check the SPF 10-DNS-lookup limit. Each include, a, mx, ptr, exists and redirect counts toward the limit; exceed it and SPF produces a PermError.
To inspect the published record:
dig +short TXT example.com
To expand includes and inspect where lookups come from, query the include's TXT records and count them. If you hit the lookup limit, flatten or replace includes with explicit ip4/ip6 entries from the provider's documentation.
Note: standard forwarding breaks SPF because the forwarder’s IP is not in your SPF. To survive forwarding, rely on DKIM or ARC technologies where available.
2) DKIM — use cPanel to generate keys and publish the selector record
- In cPanel, open "Email Deliverability" and check the domain. cPanel will propose DKIM and SPF records if they are missing or broken.
- If cPanel manages DNS for that domain, use the automatic option to install the DKIM record. If DNS is external, copy the DKIM public-key TXT that cPanel shows and add it in "Zone Editor".
A DKIM TXT name usually looks like this (selector may differ):
selector1._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=MIIB..."
- Note the selector name cPanel uses (the left-hand label before ._domainkey). When you rotate keys, add the new selector and update your MTA to sign with the new selector before removing the old one.
To verify the DKIM record exists:
dig +short TXT selector1._domainkey.example.com
DKIM provides authentication that survives simple forwarding (so long as the signature remains intact) and is one of the two mechanisms DMARC accepts for alignment.
3) DMARC — publish, monitor, then enforce
- Publish a DMARC TXT record at _dmarc.example.com. Start with a monitoring policy while you gather reports.
Example initial DMARC record (monitoring only):
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; pct=100"
- Collect and inspect aggregate reports (rua) from receivers to identify sources that fail SPF or DKIM alignment. Only after you are confident that legitimate sending sources authenticate should you move p=quarantine or p=reject.
- Remember: DMARC passes when either: SPF passes with alignment, or DKIM passes with alignment. Fix failing senders rather than bypassing checks.
To check the DMARC record:
dig +short TXT _dmarc.example.com
4) PTR / reverse DNS — set it with the IP owner, not in cPanel
- Choose the hostname you will announce in HELO/EHLO, for example mail.example.com.
- In your domain DNS (cPanel "Zone Editor" or WHM Edit DNS Zone), ensure mail.example.com has an A (or AAAA) record pointing to the sending IP:
mail.example.com. A 203.0.113.10
- PTR records live in the reverse zone controlled by the IP owner (your VPS or datacenter). Request that the provider set the PTR of 203.0.113.10 to mail.example.com. You cannot reliably set PTR through your domain DNS unless the IP owner delegates the reverse zone to your DNS provider.
- After the provider sets the PTR, verify forward-confirmed reverse DNS (FCrDNS): the PTR should point to mail.example.com, and mail.example.com should resolve back to the same IP.
To check PTR and FCrDNS:
host 203.0.113.10
# or
dig -x 203.0.113.10 +short
Receivers such as Gmail and Microsoft prefer correct rDNS and a HELO/EHLO that matches a forward-resolving hostname. Mismatch increases the chance of delivery problems.
5) Test, read headers, and iterate
- Send test messages to a Gmail or Microsoft account you control and inspect the full headers. Look for Authentication-Results to see SPF, DKIM and DMARC pass/fail states.
- Use the DNS commands above to verify records from public resolvers.
- Use DMARC aggregate reports (rua) to find senders that fail; fix their SPF/DKIM configuration or remove them from your sending list.
If SPF fails because of forwarding, ensure DKIM signs messages or use ARC if your infrastructure supports it. If lookups exceed the SPF limit, flatten or condense includes.
Final notes
If you host on Gocelerus, note that Gocelerus is cPanel web hosting for Southeast Asia, serving Indonesia and Cambodia first; servers are in Singapore, with NVMe storage, LiteSpeed web server and Imunify360 security; daily backups are included and moving an existing website to Gocelerus is free (the team does the migration). Plans and prices are at https://gocelerus.com/pricing.
Sources
Manage your cPanel servers from one dashboard
Connect your WHM to Gocelerus and manage PHP, SSL, and WordPress across all your cPanel accounts from one place.