Freshdesk email authentication

Freshworks’ support desk product.

SPF record

Add Freshdesk to your domain's SPF record with this include:

include:email.freshdesk.com

A complete record for a domain sending only through Freshdesk:

v=spf1 include:email.freshdesk.com ~all

What it costs you

7 of your 10 DNS lookups. The include: itself costs one, and Freshdesk's record chains to 6 more. Behind it are 70 IP ranges.

At 7 lookups this is an expensive include. If your record is near the limit, this is one of the first places to look — see too many DNS lookups.

Live record

This is what email.freshdesk.com published when this page was generated:

v=spf1 include:sendgrid.net include:fdspfus.freshemail.io include:fdspfeuc.freshemail.io include:fdspfind.freshemail.io include:fdspfaus.freshemail.io ~all

DKIM

Enable DKIM inside Freshdesk and publish the selector record it generates. DKIM matters more than SPF for deliverability, because a DKIM signature survives forwarding while SPF does not — see how selectors work.

DMARC

Neither SPF nor DKIM protects the address your recipients actually see until DMARC ties them to it. Once Freshdesk is authenticating, publish a DMARC record — start at p=none with a reporting address and tighten from there.

Generate a DMARC record →

Check it worked

DNS changes take minutes to hours to propagate. Once published, run the domain through the checker — it resolves the full include chain and reports the real lookup count.