include:mail.zendesk.com lets Zendesk send support notifications and agent replies as your own support address. Without it, Zendesk sends from its own domain and recipients may see “via”. Zendesk checks for it in the first layer of your record — directly in it, not inside another include — and recommends ending with -all.
v=spf1 include:mail.zendesk.com -all
| Belongs to | Zendesk Support email |
| Needed on your domain? | Yes — mail from it uses your domain as the envelope sender, so SPF checks this record |
What it costs, and is it in your record?
We measure include:mail.zendesk.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Zendesk’s is there and what it costs.
What it covers
Support notifications and agent replies Zendesk sends as your external support address, such as help@yourcompany.com. Recommended, not required, for the Zendesk Connector for Gmail.
Do you need it?
Yes, if you want Zendesk to send as your domain: it switches to your domain only once your SPF record authorises it. It works only for your own domain — not @gmail.com or @yahoo.com addresses.
Common mistakes
- Putting it inside another include — Zendesk needs it in the “first-layer lookup”.
- More than one SPF record, or any other include in the record that does not resolve: verification fails.
- Keeping the outdated include:smtp.zendesk.com or include:support.zendesk.com — Zendesk flags them.
Includes it replaced
include:smtp.zendesk.com and include:support.zendesk.com are outdated: they may still work, but Zendesk shows a warning for them.
Questions
Can I flatten my record with Zendesk in it?
Zendesk supports macros and redirect=, and says flattening services work but “may be less stable” — and its include still has to be found in the first layer.
Sources
Checked on 26 September 2026 against these official sources:
- Allowing Zendesk to send email on behalf of your email domain — support.zendesk.com