To let iCloud+ Custom Email Domain send as you, add include:icloud.com to your SPF.
Host @. Apple says if you already have SPF, add include:icloud.com before ~all. It authorises iCloud Mail to send for your domain. Measured on 5 Nov 2026, the include costs 5 of your 10 SPF lookups, leaving 5 for everything else.
- Include
- icloud.com
- Vendor’s record
- v=spf1 include:icloud.com ~all
- Where it goes
- Your domain’s SPF record (@)
- Needed on your root?
- Yes, if you send through it from your domain
- Lookups (measured)
- 5 of 10
- Ranges published
- 16 ip4 · 8 ip6
- Category
- Mailbox provider
What include:icloud.com expands to live, 5 Nov 2026
v=spf1 redirect=_spf.icloud.com
Counted as RFC 7208 §4.6.4 does: the include itself plus every nested include, a, mx, ptr, exists and redirect. Includes can change at any time; this page re-measures daily.
Adding it next to another service
A domain has exactly one SPF record, so add the include to the record you already have. With Google Workspace, for example:
v=spf1 include:_spf.google.com include:icloud.com ~all
DKIM for iCloud+ Custom Email Domain
A CNAME at sig1._domainkey pointing to sig1.dkim.<your domain>.at.icloudmailadmin.com.
How it affects DMARC
DMARC passes when SPF or DKIM passes for a domain aligned with your From address. With iCloud+ Custom Email Domain sending from your domain, its include lets SPF pass and align; DKIM signing with your domain gives you a second, forwarding-proof way to pass.
Other mailbox provider services
Sources
- Apple Support: Custom email domain DNS records · checked 5 Oct 2026
- RFC 7208 §4.6.4: DNS lookup limits · checked 5 Oct 2026
peekip isn’t affiliated with iCloud+ Custom Email Domain; follow the vendor’s own setup page, which shows the exact values for your account.