Email senders
Zendesk DMARC setup: SPF include and DKIM CNAMEs
How Zendesk authenticates your domain with an SPF include and two DKIM CNAME records, and which setup mistakes cause DMARC and delivery failures.
SPF include for Zendesk
include:mail.zendesk.com
Zendesk does not require this include. If you use it, add it to the SPF record you already have: a domain must publish only one.
- DNS lookups it uses
- 1 of 10
- Needed in your SPF record
- No
- Last checked in DNS
- 2026-11-11
DKIM for Zendesk
- Selectors
- zendesk1 zendesk2
- How to enable it
- Two CNAME records on each external domain: zendesk1._domainkey points to zendesk1._domainkey.zendesk.com and zendesk2._domainkey points to zendesk2._domainkey.zendesk.com. Then turn on Custom domain for DKIM in Admin Center.
Zendesk can sign with your domain once you set it up
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Zendesk’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- Zendesk does not document this.
Sending ranges of Zendesk
Use these to recognize Zendesk in your reports. They change over time, so do not copy them into your SPF record.
- 216.198.0.0/18
- 188.172.128.0/20
- 192.161.144.0/20
- 185.12.80.0/22
- 103.151.192.0/23
Updated 2026-11-15
Does your domain authorize Zendesk?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Zendesk documentation
- Zendesk: Allowing Zendesk to send email on behalf of your email domain
- checked 2026-11-09
- Zendesk: Digitally signing your email with DKIM
- checked 2026-11-09
- Zendesk: How do I know if my DKIM records are configured correctly?
- checked 2026-11-09
- Zendesk: Troubleshooting email deliverability
- checked 2026-11-09
- Zendesk: Troubleshooting email error messages on forwarding, SPF, DNS, and TXT records
- checked 2026-11-09
- Zendesk: Setting up the authenticated SMTP connector
- checked 2026-11-09
How it authenticates
Zendesk DMARC setup takes two DNS changes when you send from your own address, such as support@example.com.
The first is SPF, the list of servers allowed to send for your domain. Zendesk calls SPF optional and highly recommended. You add its include to the one SPF record your domain already has.
The second is DKIM, a signature that lets receivers confirm the message came from your domain. Each external domain gets two CNAME records, one for each DKIM selector. You then turn on Custom domain for DKIM in Admin Center, under Channels > Talk and email > Email. The records point to keys that Zendesk hosts.
Zendesk's SMTP connector article states that, after this setup, it signs with your domain in the d= tag.
What to watch for
Order matters. Publish both CNAMEs before you enable the option, because Zendesk warns that the reverse causes delivery failures. DNS changes can take a few hours to a day.
The Zendesk help articles listed as sources here do not state its return path, the bounce address that SPF checks. You cannot assume SPF passes DMARC alignment here, so treat DKIM on your domain as the route to rely on. Your aggregate reports show which domain SPF checked.
Two SPF records invalidate SPF, so merge the include into the existing one. It must sit directly in your domain's record, because Zendesk requires it in the first-layer lookup. The older include:smtp.zendesk.com and include:support.zendesk.com trigger an outdated-record warning.
Zendesk’s example ends in -all; use it only after authorizing every sender. Preserve existing DMARC and report addresses. For a first policy, monitor at p=none before you tighten the policy.
Zendesk has no built-in DKIM validator, so test each selector separately with the DKIM checker.
If you relay through the SMTP connector, your mail service does the final sending. Test that it does not overwrite the signature Zendesk added.