To let Zendesk send as you, add include:mail.zendesk.com to your SPF.
Zendesk notes include:mail.zendesk.com must be in the first layer of lookups (directly in your record, not nested in another include). Zendesk verifies this record when you add a support address. Measured on 4 Nov 2026, the include costs 1 of your 10 SPF lookups, leaving 9 for everything else.
- Include
- mail.zendesk.com
- Vendor’s record
- v=spf1 include:mail.zendesk.com -all
- Where it goes
- Your domain’s SPF record (@)
- Needed on your root?
- Yes, if you send through it from your domain
- Lookups (measured)
- 1 of 10
- Ranges published
- 5 ip4 · 0 ip6
- Category
- Help desk
What include:mail.zendesk.com expands to live, 4 Nov 2026
v=spf1 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:216.198.0.0/18 ~all
Counted as RFC 7208 §4.6.4 does: the include itself plus every nested include, a, mx, ptr, exists and redirect. Includes can change at any time; this page re-measures daily.
Adding it next to another service
A domain has exactly one SPF record, so add the include to the record you already have. With Google Workspace, for example:
v=spf1 include:_spf.google.com include:mail.zendesk.com ~all
How it affects DMARC
DMARC passes when SPF or DKIM passes for a domain aligned with your From address. With Zendesk sending from your domain, its include lets SPF pass and align; DKIM signing with your domain gives you a second, forwarding-proof way to pass.
Other help desk services
Sources
- Zendesk: Allowing Zendesk to send email on behalf of your domain · checked 5 Oct 2026
- RFC 7208 §4.6.4: DNS lookup limits · checked 5 Oct 2026
peekip isn’t affiliated with Zendesk; follow the vendor’s own setup page, which shows the exact values for your account.