Email senders
Freshdesk DMARC setup: DKIM, SPF and alignment
How Freshdesk signs support mail with DKIM, when SPF is optional, and the setup mistakes that break verification or DMARC for Freshdesk customers.
SPF include for Freshdesk
include:email.freshdesk.com
Freshdesk does not require this include. If you use it, add it to the SPF record you already have: a domain must publish only one.
- DNS lookups it uses
- 7 of 10
- Needed in your SPF record
- No
- Last checked in DNS
- 2026-11-11
DKIM for Freshdesk
- Selectors
- Freshdesk does not document this.
- How to enable it
- Four CNAME records per domain, generated under Admin > Channels > Email > Advanced Settings > Configure DKIM. Mandatory on the Freshworks mail server. Selector names are not documented.
Freshdesk signs with your domain
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Freshdesk’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- Freshdesk does not document this.
Sending ranges of Freshdesk
Use these to recognize Freshdesk in your reports. They change over time, so do not copy them into your SPF record.
- 149.72.0.0/16
- 159.183.0.0/16
- 167.89.0.0/17
- 168.245.0.0/17
- 134.128.64.0/18
- 50.31.32.0/19
- 159.26.176.0/20
- 192.254.112.0/20
Updated 2026-11-15
Does your domain authorize Freshdesk?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Freshdesk documentation
- Freshdesk: Configuring DKIM records
- checked 2026-11-09
- Freshdesk: Create an SPF record to ensure proper email delivery
- checked 2026-11-09
- Freshdesk: Configure advanced email settings
- checked 2026-11-09
- Freshdesk: Troubleshoot issues with setting up custom email server
- checked 2026-11-09
- Freshdesk: Converting support emails into tickets
- checked 2026-11-09
How it authenticates
Freshdesk DMARC setup depends on the sending server. Replies through the default Freshworks mail server require DKIM (DomainKeys Identified Mail) domain verification. Freshdesk signs with your domain, enabling DMARC alignment.
Go to Admin > Channels > Email > Advanced Settings > Configure DKIM. Freshdesk generates four CNAME records. Publish them in your DNS and click Verify. Addresses on one domain share a setup. Each extra domain needs its own.
Freshdesk says SPF (Sender Policy Framework) is not required once DKIM is set up. SPF counts for DMARC only when the envelope-from domain, where bounces go, aligns with your From domain. Freshdesk does not document that address, so plan on DKIM to make DMARC pass.
If you send through Gmail, Microsoft 365 or your own server, Freshdesk does not require its DKIM setup, though it recommends it. Receivers then judge what that server signs and sends, so authenticate the domain there too.
What to watch for
A public address fails on the Freshworks server with Since you have connected Freshworks mail server, your email alias cannot be in public domain. Freshdesk cannot sign for Gmail or Microsoft domains. Choose the matching server type, or use an address on your own domain.
Freshdesk's example uses fwdkim1. On a DNS host that appends your domain, enter only that label. A doubled domain or spaces prevent verification.
For Domain verified in other account, check the affected account with support before deleting records still used by another account. Use one CNAME per owner name, never combine targets; ask Freshdesk support if accounts require different targets at the same name.
Freshdesk publishes no selector names. Read s= in a sent message, then test it with the DKIM checker.
If you add include:email.freshdesk.com, keep a single SPF record. When we checked in November 2026, it used seven of the ten DNS lookups SPF allows. Freshdesk lets you include only your data center's record instead.
Confirm aligned Freshdesk DKIM in reports. Preserve existing DMARC and report addresses. For a first policy, monitor at p=none before you tighten the policy.