To let Freshdesk send as you, add include:email.freshdesk.com to your SPF.
Add it to your existing record if you have one. Freshdesk documents it for sending replies from your support address. Measured on 5 Nov 2026, the include costs 7 of your 10 SPF lookups, leaving 3 for everything else.
- Include
- email.freshdesk.com
- Vendor’s record
- v=spf1 include:email.freshdesk.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)
- 7 of 10
- Ranges published
- 70 ip4 · 0 ip6
- Category
- Help desk
What include:email.freshdesk.com expands to live, 5 Nov 2026
v=spf1 include:sendgrid.net include:fdspfus.freshemail.io include:fdspfeuc.freshemail.io include:fdspfind.freshemail.io include:fdspfaus.freshemail.io ~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:email.freshdesk.com ~all
How it affects DMARC
DMARC passes when SPF or DKIM passes for a domain aligned with your From address. With Freshdesk 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
- Freshdesk: Creating an SPF record · checked 5 Oct 2026
- RFC 7208 §4.6.4: DNS lookup limits · checked 5 Oct 2026
peekip isn’t affiliated with Freshdesk; follow the vendor’s own setup page, which shows the exact values for your account.