SMTP2GO authenticates a domain with three CNAMEs; the second, to dkim.smtp2go.net, carries the DKIM key. Since 11 April 2025 it sends only from verified senders.
| Whose | SMTP2GO — sending service |
| Selector | the name SMTP2GO shows |
| Published as | A CNAME to dkim.smtp2go.net, the second of the three records SMTP2GO gives |
| Key | dkim.smtp2go.net answers with a 2048-bit key |
| Before you set it up | A single verified sender address is signed with SMTP2GO’s own key — “via smtpcorp.com” or “via smtp2go.com” |
| Where to find it | Sending → Verified Senders → Sender domains |
| Can it go? | Once nothing sends through SMTP2GO for the domain. |
Is SMTP2GO’s key on your domain?
SMTP2GO makes a selector for each account. Enter a domain and the selector it gave you — or paste the DKIM-Signature header of a message it sent — and we check the key, and name every other key the domain publishes.
The records
Use the names SMTP2GO shows; the targets are the same for everyone:
<selector>._domainkey.example.com CNAME dkim.smtp2go.net
em<number>.example.com CNAME return.smtp2go.net
Common mistakes
- Cloudflare’s proxy or CNAME flattening switched on — both must be off for the records to verify.
- Entering the full name at hosts that append the domain.
What changed
- 11 April 2025 — Sending only from verified senders.
Sources
Checked on 27 September 2026 against these official sources:
- Verified Senders — support.smtp2go.com
- SPF DKIM and DMARC Overview — support.smtp2go.com
- DNS Setup for Cloudflare — support.smtp2go.com