include:spf.smtp2go.com lists SMTP2GO’s relay servers. Since June 2019 a verified sender domain handles SPF for you: its mail carries a return-path on a subdomain of yours (em123.yourdomain.com) that points to SMTP2GO with a CNAME — “There is no need to update your SPF record.” The include is needed only if you turn on “Maintain Return-Path”.
v=spf1 include:spf.smtp2go.com ~all
| Belongs to | SMTP2GO relay and API |
| Needed on your domain? | Only in some set-ups — by default SPF checks a different domain for its mail |
What it costs, and is it in your record?
We measure include:spf.smtp2go.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether SMTP2GO’s is there and what it costs.
What it covers
Mail relayed through SMTP2GO by SMTP or API.
Do you need it?
Usually not. “Adding a verified sender domain means that SPF and DKIM are automatically handled by us”: the return-path is the em subdomain, a CNAME to return.smtp2go.net.
The exception is “Maintain Return-Path” (Settings → Sending Options → Advanced), meant “only … in rare situations” such as email-to-fax. Those messages keep your own address as the return-path, so then “add include:spf.smtp2go.com to the SPF record of your sender domain name”.
Its other forms
| Include | For |
|---|---|
return-alt.smtp2go.net | The return-path CNAME target to use if you need its SPF record to end with -all (return.smtp2go.net ends with ~all). |
Common mistakes
- A DNS host that will not take the underscores the DKIM and return-path names need.
- Adding the include out of habit — without Maintain Return-Path it costs a lookup and does nothing.
Includes it replaced
Before 10 June 2019, SMTP2GO used your From address as the return-path and asked for the include on your domain.
Sources
Checked on 26 September 2026 against these official sources:
- Verified Senders — support.smtp2go.com
- Maintaining the Return path — support.smtp2go.com
- Sender Domain Update — smtp2go.com