Email senders
ZeptoMail DMARC setup: DKIM and the bounce domain
How ZeptoMail authenticates your domain with a DKIM key and a bounce CNAME, why SPF is not needed to verify it, and what breaks DMARC alignment.
SPF include for ZeptoMail
ZeptoMail does not need an SPF include on your domain.
DKIM for ZeptoMail
- Selectors
- ZeptoMail does not document this.
- How to enable it
- Copy the DKIM TXT host and value from Domains. When adding a new key, generate a selector or enter your own and choose a 1024-bit or 2048-bit key.
ZeptoMail 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 ZeptoMail’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- A subdomain configured with the bounce CNAME, such as bounce.example.com
Sending ranges of ZeptoMail
Use these to recognize ZeptoMail in your reports. They change over time, so do not copy them into your SPF record.
ZeptoMail does not document this.
Does your domain authorize ZeptoMail?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
ZeptoMail documentation
- Zoho CPaaS: Domain Addition & Verification
- checked 2026-11-09
- Zoho Blog: No more SPF for domain verification in ZeptoMail
- checked 2026-11-09
- Zoho CPaaS: DMARC Policy
- checked 2026-11-09
- Zoho CPaaS: Domain Association in Agent
- checked 2026-11-09
- Zoho CPaaS: Cloudflare DNS configuration
- checked 2026-11-09
- Zoho Blog: ZeptoMail Is Now Zoho CPaaS
- checked 2026-11-09
How it authenticates
ZeptoMail DMARC setup needs two DNS records to verify each sending domain, plus your own DMARC TXT record at _dmarc.example.com. Zoho renamed the product Zoho CPaaS in September 2026 and says existing configuration keeps working.
The first record is a DKIM key, published as a TXT record at <selector>._domainkey on your domain. Zoho lists the TXT host and value in the Domains section. When you add a new key, you auto-generate a DKIM selector or type your own, and you pick a 1024-bit or 2048-bit key.
The second record is a CNAME on a subdomain such as bounce. It sets the return path, the address that collects bounced mail. Zoho points the matching SPF data at that subdomain for you, so its current help says an SPF record is not required to verify the domain.
The domain cannot send until it is verified, and DNS changes can take 24 to 48 hours to appear.
What to watch for
Your From domain is example.com and your return path is bounce.example.com. Those names differ, so SPF alignment depends on the aspf tag. Relaxed mode, the default, accepts the subdomain. Strict mode (aspf=s) rejects it, and DKIM alignment has to carry the message through DMARC.
Zoho's DMARC Policy help still says domains are verified with SPF and DKIM. Follow the domain help, updated more recently, when the two disagree.
On Cloudflare, set the proxy status of the CNAME to DNS only, as Zoho's DNS guide instructs.
After you create the bounce address, use it in your SMTP or API configuration. Zoho lists this as a required step.
When you rotate keys, verify the existing DKIM key first. Zoho allows up to two new keys, and each one needs its own verification. See DKIM rotation, then confirm the published key with the DKIM checker.