Email senders
SMTP2GO DMARC setup: how SPF and DKIM align
How SMTP2GO authenticates a verified sender domain with CNAME records, when you need its SPF include, and what breaks DMARC alignment.
SPF include for SMTP2GO
include:spf.smtp2go.com
SMTP2GO 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
- 1 of 10
- Needed in your SPF record
- No
- Last checked in DNS
- 2026-11-11
DKIM for SMTP2GO
- Selectors
- SMTP2GO does not document this.
- How to enable it
- Publish the CNAME records shown on Verified Senders to set up DKIM for your domain. Copy the hostnames from that page. Verifying a single email address does not provide aligned DKIM.
SMTP2GO 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 SMTP2GO’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- A subdomain starting with em, such as em100.example.com
Sending ranges of SMTP2GO
Use these to recognize SMTP2GO in your reports. They change over time, so do not copy them into your SPF record.
- 158.120.80.0/21
- 66.235.120.0/21
- 103.2.140.0/22
- 103.47.204.0/22
- 170.10.68.0/22
- 203.31.36.0/22
- 43.228.184.0/22
- 216.22.15.224/27
Updated 2026-11-15
Does your domain authorize SMTP2GO?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
SMTP2GO documentation
- SMTP2GO: SPF Records, How They Work and How to Set Up
- checked 2026-11-09
- SMTP2GO: Sender Domain Update
- checked 2026-11-09
- SMTP2GO: Registering a Verified Sender is Now a Required Action
- checked 2026-11-09
- SMTP2GO: How to Maintain the Return-path
- checked 2026-11-09
- SMTP2GO: What is DMARC?
- checked 2026-11-09
How it authenticates
SMTP2GO DMARC alignment starts when you verify your sender domain. You add the domain on the Verified Senders page, and SMTP2GO gives you CNAME records for your DNS. A CNAME makes one hostname point to another.
The first record starts with em and creates a subdomain such as em100.example.com. SMTP2GO uses it as the return path, the hidden address that receives bounces. SPF checks that address against a record SMTP2GO keeps up to date. DKIM, the signature on each message, comes from the same CNAME setup and uses a key for your domain.
The Return-Path can align under your domain; you manage DMARC separately. Preserve existing DMARC and report addresses. For a first policy, monitor at p=none before you tighten the policy.
What to watch for
Adding the include out of habit. SMTP2GO says normal sending from a verified domain needs no change to your SPF record. SPF is checked on the em subdomain, so an extra SPF include on your root domain does not help alignment and spends one of your ten DNS lookups.
Maintain Return-Path. For the recipient domains added here, this exception skips VERP (Variable Envelope Return Path) and keeps your original sender address. SMTP2GO then requires include:spf.smtp2go.com in that sender domain’s SPF record. Merge it into the existing single record.
Strict alignment. With the aspf tag set to aspf=s in your DMARC record, the em subdomain no longer matches your From domain exactly. SPF alignment fails, and DMARC depends on DKIM alone.
Single sender emails. SMTP2GO lets you verify one address instead of a domain. It warns that the domain then will not align for SPF and DKIM.
Copying records from elsewhere. SMTP2GO shows the exact records on your Verified Senders page. Copy them from there, then confirm the result with the DKIM checker.