11 Nov 2026 · 6 min read · EN
How to make third‑party senders pass DMARC by configuring DKIM in cPanel
If you send email through a third‑party service, have them sign messages with your domain (or use a dedicated subdomain) and publish the matching DNS records in cPanel so DKIM aligns with your From: address and DMARC can pass.
By Tim Gocelerus
Problem
Messages sent by a third‑party (SendGrid, Mailchimp, etc.) can fail DMARC because the message isn’t signed with your domain. You need DKIM signatures that both pass and align with the From: domain (or a working SPF alignment), otherwise receivers will fail DMARC.
How DMARC alignment works (short)
DMARC requires either SPF or DKIM to both pass and align with the visible From: domain. If either an aligned SPF or an aligned DKIM passes, the message passes DMARC. For third‑party senders DKIM is usually the better choice because DKIM survives simple forwarding when SPF often does not.
Decide your approach first
- Ask the third‑party to sign outgoing mail with your domain (recommended). They provide DKIM selectors and DNS records you add to your DNS.
- Or use a dedicated subdomain for that service (for example, marketing.example.com) and have the third‑party send from that subdomain. Then DMARC/SPF/DKIM for the subdomain are under your control.
Audit real messages first: collect a few recent messages sent by the service, inspect the headers, and note the Return‑Path (envelope sender) and any DKIM‑Signature headers. The receiver checks SPF against the envelope sender, not necessarily the visible From address, so do not assume they’re the same.
What to ask the service to do
- Provide DKIM signing using your domain (not just their default domain). They’ll usually give you either:
- one or more CNAME records that point to their DKIM key (common), or
- a TXT record for selector._domainkey.yourdomain containing the public key.
- Provide the exact selector name(s) and record values to add to your DNS.
- Confirm what value will appear in the DKIM header (the d= tag) so you can verify alignment with your From: domain.
Add the records in cPanel (Zone Editor)
Use the exact values the provider gives you. Do not invent selectors or keys.
- Log in to cPanel and open Zone Editor.
- For the domain, click Manage.
- Add the records the provider supplied:
- If the provider gave CNAME authentication, add the CNAME records exactly as provided. Example template (replace with values from the provider):
Name: selector._domainkey.example.com.
Type: CNAME
Record: selector.domainkey.provider.com.
- If the provider gave a TXT DKIM record, add a TXT record. Example template:
Name: selector._domainkey.example.com.
Type: TXT
Record: v=DKIM1; k=rsa; p=PUBLIC_KEY_FROM_PROVIDER
- Save each record. CNAME targets commonly end with a dot in DNS editors; follow the provider’s exact format.
Use cPanel Email Deliverability to check and fix common issues
- In cPanel open Email Deliverability. It will report missing or malformed DKIM/SPF for the selected domain.
- If Email Deliverability suggests adding or repairing records, cross‑check those suggestions with the values the third‑party provided. Do not replace a provider’s DKIM records with a different value.
Verify DKIM signing and alignment
- Send a test message through the third‑party service to an account you control (Gmail, Outlook, or a mailbox on the domain).
- Inspect the received message headers and look for a DKIM‑Signature header and an Authentication‑Results header. In the DKIM‑Signature header note the d= (domain) and s= (selector) values; in Authentication‑Results look for dkim=pass.
- For alignment, the d= value must match the domain in the From: header (exact match for strict alignment, or same organizational domain for relaxed alignment as your DMARC policy specifies). If d= shows the third‑party’s domain rather than your domain, DKIM will not align.
If DKIM passes but the d= value is not your domain, go back to the provider and request signing with your domain or use a dedicated subdomain they can sign for you.
SPF: why it’s often not the long‑term fix for third‑parties
SPF can pass and align, but it commonly breaks with forwarding and it has a hard lookup budget: an SPF record evaluation may perform up to 10 DNS‑querying mechanisms (include, a, mx, ptr, exists, redirect). Exceeding that budget causes SPF to produce a permanent error. Also, you must publish a single SPF TXT record for the name — multiple TXT SPF records are an error.
Best practices when multiple senders exist:
- Audit message headers to determine the envelope sender used for SPF checks.
- Prefer DKIM signing by the third‑party rather than bloating your SPF with many includes.
- If you must include multiple services in SPF, consolidate into a single TXT record and avoid nested includes that push you past the 10‑lookup limit.
- Use ip4/ip6 mechanisms where the provider allows listing IPs directly (literal addresses don’t count toward the lookup limit), but only if the provider publishes stable IPs and they tell you to do this.
- If SPF gets complex, consider moving that service to a dedicated subdomain with its own SPF/DKIM/DMARC so the main domain’s record stays small.
cPanel’s Zone Editor and Email Deliverability tools will help you keep a single SPF record and show missing or conflicting entries; use those tools to avoid creating multiple TXT records for the same name.
Troubleshooting checklist
- Verify the DKIM DNS record exists and exactly matches the provider’s values.
- Send test mail and inspect headers for DKIM‑Signature d= and s= and for Authentication‑Results dkim=pass.
- Confirm d= matches the From: domain (alignment). If not, request the provider sign with your domain or use a dedicated sending subdomain.
- If using SPF as backup, confirm you have a single SPF TXT record and you are under the 10 lookup budget. If not, reduce includes or use a subdomain.
- Recheck in cPanel Email Deliverability and in the provider’s interface (many providers show verification status once DNS propagates).
Summary
For third‑party senders, prefer having the service sign messages with your domain’s DKIM key (or sign a dedicated subdomain you control). Add the exact DKIM CNAME or TXT records the provider gives you in cPanel’s Zone Editor, use Email Deliverability to spot obvious DNS mistakes, and verify by inspecting message headers for a passing DKIM with a matching d= value. Audit real messages first so you know which domain the receiver checks for SPF.
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).
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.