include:email.freshdesk.com authorises Freshdesk’s mail servers in every data centre — and costs as much: it includes SendGrid and four regional records, seven lookups in all. Freshdesk itself says it “consume[s] too many lookups” and points to the include for your own data centre. With Freshdesk’s DKIM records set up, SPF “is not required”.
v=spf1 include:email.freshdesk.com ~all
| Belongs to | Freshdesk (Freshworks) support email |
| Needed on your domain? | It depends on how you use it — see below |
What it costs, and is it in your record?
We measure include:email.freshdesk.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Freshdesk’s is there and what it costs.
What it covers
Support mail Freshdesk sends from your support address through its default mail servers.
Do you need it?
Freshdesk says SPF configuration “is not required if you already have DKIM setup” — four CNAME records it generates, which it describes as covering the SPF check too. Domain verification is mandatory when you use Freshdesk’s default mail server.
If you do add SPF, use your data centre’s include rather than the global one.
Its other forms
| Include | For |
|---|---|
fdspfus.freshemail.io | US data centre. |
fdspfeuc.freshemail.io | EU data centre. |
fdspfind.freshemail.io | India data centre. |
fdspfaus.freshemail.io | Australia data centre. |
Common mistakes
- The global include in a record that already has several — seven lookups is most of the limit.
- Spaces in the DKIM CNAME values, or the domain doubled in GoDaddy’s host field.
Sources
Checked on 26 September 2026 against these official sources:
- Create an SPF record to ensure proper support email delivery — support.freshdesk.com
- Freshdesk Email domain verification using DKIM records — support.freshdesk.com