# SPF record for SMTP2GO

URL: https://iblockspam.com/spf/smtp2go
Last updated: 2026-10-22

Include: None needed (return-path CNAME)
Where it goes: Not needed (return-path CNAME)
DNS lookups: depends on your account

You don't need to change your SPF record for SMTP2GO. When you verify a sender domain, SMTP2GO gives you three CNAME records; the first is the return-path subdomain (such as em12345.example.com), pointing to return.smtp2go.net, and it covers SPF. SMTP2GO dropped the SPF include requirement in 2019 when it moved to VERP return paths.

## Example records

- Return-path CNAME (not TXT); your host name comes from SMTP2GO (CNAME, host em12345): `return.smtp2go.net`
- If you need the return path's SPF to end in -all (CNAME, host em12345): `return-alt.smtp2go.net`
- Your main domain on Microsoft 365 stays as it is (TXT, host @): `v=spf1 include:spf.protection.outlook.com -all`

## Notes

- SMTP2GO recommends a TTL of 14400 seconds (4 hours) for these records.
- Since 11 April 2025, SMTP2GO requires every email to come from a verified sender: a verified domain or a single verified address.
- If company policy rules out CNAME records, SMTP2GO says it can enable TXT and MX records instead on request.

## How to add it

- In the SMTP2GO dashboard, go to Sending, Verified Senders, Sender domains, click Add sender domain and enter the domain you send from.
- Add the three CNAME records shown: the return path (SPF), DKIM and the link-tracking domain. SMTP2GO can add them for you through Entri, or you add them by hand.
- If your DNS host is Cloudflare, set each record to DNS only and turn off CNAME flattening, as SMTP2GO's Cloudflare guide says.
- Click Verify. The domain is set up once its status shows Verified. Leave your main domain's SPF record unchanged.

## DKIM and DMARC

DKIM is covered by the second CNAME, which points to `dkim.smtp2go.net`; see our [SMTP2GO DKIM page](https://iblockspam.com/dkim/smtp2go). Without a verified domain, SMTP2GO signs with its own domain and Gmail can show "via smtpcorp.com". DMARC is a separate TXT record you add yourself.

## Common mistakes

- Adding an SMTP2GO include to your root SPF record because an old guide said so. SMTP2GO says you don't need to update your SPF record.
- Proxying the CNAMEs through Cloudflare or leaving CNAME flattening on, which stops them from verifying.
- Verifying only a single sender address when you could verify the domain. Single sender emails don't use your domain for DKIM or SPF.

**Q: Do I need to add SMTP2GO to my SPF record?**
No. SMTP2GO says SPF is handled automatically once your sender domain is verified: the first of its three CNAME records is the return-path subdomain, and receivers check SPF there. Your main domain's SPF record stays as it is.

**Q: Can SMTP2GO's return path use -all instead of ~all?**
Yes. SMTP2GO says to point the return-path CNAME at `return-alt.smtp2go.net` instead of `return.smtp2go.net` if you need a hard fail (`-all`). When we checked on 22 October 2026, those two names published `~all` and `-all` records respectively.

**Q: What are SMTP2GO's three CNAME records for?**
The first is the return path, used for bounces and SPF; the second is DKIM, pointing to `dkim.smtp2go.net`; the third is the link-tracking domain, pointing to `track.smtp2go.net`, which gets a certificate automatically so tracked links use https.

Sources:
- SMTP2GO Support: SPF, DKIM and DMARC overview: https://support.smtp2go.com/hc/en-gb/articles/28543815517209-SPF-DKIM-and-DMARC-Overview
- SMTP2GO Support: Verified Senders: https://support.smtp2go.com/hc/en-gb/articles/115004408567-Verified-Senders
- SMTP2GO Support: DNS setup for Cloudflare: https://support.smtp2go.com/hc/en-gb/articles/360022578154-DNS-Setup-for-Cloudflare

---

Source: iBlockSpam, https://iblockspam.com/spf/smtp2go (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt