How do I set up Zendesk so its email passes DMARC?
Publish the records Zendesk documents for your domain.
Last read from the sources at the foot of this page.
What does Zendesk ask me to publish?
However, if you allow Zendesk to send email on behalf of your email domain, Zendesk stops sending messages from zendesk.com
Zendesk prints these values in its own documentation, the same for every customer.
include:mail.zendesk.comzendesk1._domainkey.zendesk.comzendesk2._domainkey.zendesk.comHow do I add Zendesk to the SPF record I already have?
SPF implementations MUST limit the total number of those terms to 10 during SPF evaluation, to avoid unreasonable load on the DNS. If this limit is exceeded, the implementation MUST return "permerror".
Add include:mail.zendesk.com inside the one SPF record you have, before its last word, and keep every service already in it. Never add a second SPF record: two make the check fail for every message.
An SPF record may make at most 10 DNS lookups. Each include counts, and so do the includes inside it. Past 10, the check fails, so remove services you no longer use before you add a new one.
Will p=reject block Zendesk email?
Digitally signing outbound email is supported only if you use an external email domain for your Zendesk email
Not once Zendesk signs your email with your domain's DKIM key. DMARC passes when a message passes DKIM or SPF for your own domain, and the DKIM records Zendesk gives you are on your domain.
Zendesk signs your mail with DKIM as your domain only when you use your own email domain for Zendesk email and publish the two DKIM records.
Zendesk rotates its DKIM keys every quarter. The two CNAME records follow the current key, so nothing needs to change when it rotates.
Before you raise your policy, read your DMARC reports and check that email from Zendesk passes.
Where does this come from?
- Zendesk: Allowing Zendesk to send email on behalf of your email domainsupport.zendesk.comRead 14 October 2026
- Zendesk: Digitally signing your email with DKIMsupport.zendesk.comRead 14 October 2026
- RFC 7208, Sender Policy Frameworkrfc-editor.orgRead 14 October 2026
- RFC 7489, DMARCrfc-editor.orgRead 14 October 2026
See what is open before anyone else does.
We read from outside, find each way in first, and show it with a check anyone can re-run. No access, nothing tested, no obligation.
- We read your firm from outside.
- You see what is open, with the proof for the lead finding.
- If it is worth it, you order.
What happens if you go ahead. More at getleaktrace.com/see-it-first/.
Read the transcript
- 72 hours. One domain. Nothing to install.
- Discover. Every way in, found from outside.
- Validate. Every finding, proven. Dated and checkable by anyone.
- Close. Forged email: one click per step, where we reach your DNS host and you approve it.
- You get the fix for the rest, step by step, and we re-check until it is closed.
- Monitor. On monitoring: email settings, look-alikes and new host names re-checked every hour. Alerts within the hour.
- Every paid assessment is human-verified before release.
- The AI defense layer for businesses. getleaktrace.com/see-it-first/