Email senders
Help Scout DMARC setup: DKIM, SPF and alignment
How Help Scout signs mail from your domain, why its SPF result does not align with DMARC, and which DKIM records you need to publish.
SPF include for Help Scout
Help Scout does not need an SPF include on your domain.
DKIM for Help Scout
- Selectors
- strong1 strong2
- How to enable it
- Two CNAME records on your domain: strong1._domainkey points to strong1._domainkey.helpscout.net and strong2._domainkey points to strong2._domainkey.helpscout.net. Without them, Help Scout signs for helpscout.net.
Help Scout 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 Help Scout’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- A VERP return-path address on a Help Scout domain. Help Scout does not document the exact domain.
Sending ranges of Help Scout
Use these to recognize Help Scout in your reports. They change over time, so do not copy them into your SPF record.
Help Scout does not document this.
Does your domain authorize Help Scout?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Help Scout documentation
- Help Scout: Use DKIM to Help With Email Delivery
- checked 2026-11-09
- Help Scout: Changes to SPF Requirements With Help Scout
- checked 2026-11-09
- Help Scout: Domain Changes Needed to Continue Sending Emails From Help Scout Servers
- checked 2026-11-09
- Help Scout: Create CNAME Records at Cloudflare
- checked 2026-11-09
- Help Scout: Troubleshooting Conversations in Needs Attention and Bounces
- checked 2026-11-09
How it authenticates
Help Scout DMARC setup matters when an inbox uses your own address and sends through Help Scout's servers. Inboxes on the assigned helpscoutapp.com address authenticate on that domain. Inboxes that send through your email provider over SMTP or OAuth skip this setup.
By default, Help Scout sends from helpscout.net on behalf of your domain and signs for helpscout.net. DKIM (DomainKeys Identified Mail) signs each message with a domain name. That default name differs from your From address.
To change it, publish two CNAME records at your DNS host, named strong1._domainkey and strong2._domainkey. Help Scout then signs as your domain, which gives DMARC the aligned pass it needs.
SPF (Sender Policy Framework) works differently here. Help Scout uses a VERP (variable envelope return path) address on its own domain. SPF passes for that domain and does not align with your From address.
What to watch for
While you send through Help Scout's servers, DKIM is the only route to alignment. If DKIM fails and your domain publishes p=reject, receivers can refuse the mail. Help Scout lists errors such as 5.7.26 Unauthenticated email from domain.com is not accepted due to domain's DMARC policy.
Older setups may carry include:helpscoutemail.com. Help Scout says you can safely remove it. Each include also counts toward the ten DNS lookups SPF allows.
Two DNS details need care. On Cloudflare, set both CNAME records to DNS only. Other hosts may want only the prefix in the Host field, so remove your domain from it if the lookup comes back empty.
Open Settings > Inboxes > your inbox > Outgoing Email > Test Settings. DKIM should show Active; allow up to an hour for DNS. Test strong1 and strong2 with the DKIM checker. Preserve existing DMARC and report addresses. For a first policy, monitor at p=none before you tighten the policy.