# SPF record for Freshdesk

URL: https://iblockspam.com/spf/freshdesk
Last updated: 2026-10-09

Include: include:email.freshdesk.com
Where it goes: Your support address's domain (@)
DNS lookups: 7 of 10

Freshdesk gives the SPF value v=spf1 include:email.freshdesk.com ~all. That include costs 7 DNS lookups, so Freshdesk also lists one include per data center, such as include:fdspfus.freshemail.io for the US, at 1 lookup each. Freshdesk says SPF isn't required if you've already set up DKIM.

## Example records

- Freshdesk only (Freshdesk's value) (TXT, host @): `v=spf1 include:email.freshdesk.com ~all`
- Freshdesk US data center and Microsoft 365 (TXT, host @): `v=spf1 include:spf.protection.outlook.com include:fdspfus.freshemail.io -all`
- Freshdesk EU data center and Google Workspace (TXT, host @): `v=spf1 include:_spf.google.com include:fdspfeuc.freshemail.io ~all`

## Notes

- On 9 October 2026, `email.freshdesk.com` nested all four data-center includes plus `sendgrid.net`, for 7 lookups in total.

## How to add it

- Check whether DKIM is already set up for your support domain in Freshdesk. If it is, Freshdesk says SPF isn't required.
- Otherwise, sign in where your domain's DNS is managed (Freshdesk's article says your domain name registrar) and open the TXT record on `@` that starts with `v=spf1`. Nothing is pasted into Freshdesk itself.
- Add `include:email.freshdesk.com`, or the include for your Freshdesk data center if lookups are tight: `fdspfus.freshemail.io` (US), `fdspfeuc.freshemail.io` (EU), `fdspfind.freshemail.io` (India) or `fdspfaus.freshemail.io` (Australia).
- Save, then check the live record with the SPF Checker below.

## DKIM and DMARC

Freshdesk notes that SPF configuration is not required if you already have DKIM set up, and documents DKIM records in a separate article. DKIM signed with your domain is also what DMARC can rely on when mail is forwarded.

## Common mistakes

- Adding `include:email.freshdesk.com` next to Microsoft 365, Google Workspace and a marketing tool, and going over 10 lookups. Use your data center's include instead.
- Creating a second SPF record for Freshdesk. Freshdesk says to add the include on the same line as your existing record.
- Choosing the old SPF record type because Freshdesk's article mentions "TXT or SPF records". RFC 7208 says SPF records must be published as TXT.

**Q: What is the SPF record for Freshdesk?**
Freshdesk gives `v=spf1 include:email.freshdesk.com ~all`. If an SPF record already exists, add `include:email.freshdesk.com` to it on the same line.

**Q: Why does Freshdesk's include use so many DNS lookups?**
`email.freshdesk.com` includes a record for every Freshdesk data center, plus SendGrid's. We measured 7 lookups on 9 October 2026. Freshdesk suggests including only your data center's record, such as `fdspfus.freshemail.io`, which costs 1.

**Q: Do I need SPF for Freshdesk if DKIM is set up?**
Freshdesk says SPF configuration is not required if you already have DKIM set up. Adding the include is still harmless if you have lookups to spare.

Sources:
- Freshdesk Support: Create an SPF record to ensure proper email delivery: https://support.freshdesk.com/support/solutions/articles/43170
- RFC 7208 section 3.1: DNS resource records: https://www.rfc-editor.org/rfc/rfc7208.html#section-3.1

---

Source: iBlockSpam, https://iblockspam.com/spf/freshdesk (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt