include:helpscoutemail.com let Help Scout send from your custom inbox address. Help Scout retired it in 2024: its mail now passes SPF on a return-path at Help Scout’s own servers, and Help Scout says you can remove the include. For DMARC, add Help Scout’s DKIM CNAMEs.
v=spf1 include:helpscoutemail.com ~all
| Belongs to | Help Scout |
| Needed on your domain? | No — SPF checks a different domain for its mail, not this record on yours |
What it costs, and is it in your record?
We measure include:helpscoutemail.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Help Scout’s is there and what it costs.
What it covers
Mail Help Scout sent from its servers with your custom inbox address, before 2024.
Do you need it?
No. Help Scout’s own before-and-after example removes it: v=spf1 include:_spf.google.com include:helpscoutemail.com ~all becomes v=spf1 include:_spf.google.com ~all.
Its mail now passes SPF on Help Scout’s domain, which does not align with yours — so DMARC relies on Help Scout’s DKIM CNAMEs. If you need SPF to align, send through your own mail provider (custom SMTP or OAuth).
Common mistakes
- Keeping the include: it adds nothing and costs a lookup.
Includes it replaced
Help Scout asked for include:helpscoutemail.com until 2024; it gives no exact date.
Sources
Checked on 26 September 2026 against these official sources:
- Changes to SPF Requirements With Help Scout — docs.helpscout.com