How to Set Up a Custom Email Domain with iCloud+

The short answer
Any paid iCloud+ plan lets you use a custom domain with iCloud Mail. Set it up in iCloud settings on iPhone, Mac, or at icloud.com, then add two MX records pointing to Apple's mail servers, one SPF TXT record, one DKIM CNAME, and a verification TXT Apple generates during setup. DNS typically propagates within a few hours.
Set up a custom email domain with iCloud+: the DNS records Apple needs, platform steps, family sharing limits, and what the feature can't do.
On this page
iCloud+ lets you send and receive email from an address on your own domain without paying for a separate mail host or migrating to a new platform. Apple handles delivery, DKIM signing, and spam filtering; your job is to update five DNS records at your registrar. That is the whole arrangement.
The feature is simpler than most guides make it look, but it has real limits worth knowing before you move a professional address onto it. This guide walks through every DNS record Apple needs, the setup path on each platform, what to do when verification stalls, and how iCloud custom domain compares to Google Workspace for people weighing both.
The Short Answer#
Any paid iCloud+ plan — starting at the 50 GB tier — includes custom email domain support. You bring a domain you already own; Apple does not register or sell domains. You can add up to five domains to a single Apple ID, with up to three email addresses per domain per person.
The DNS side requires five records. Apple provides the exact values after you enter your domain. You add them at your registrar, return to iCloud settings, and complete the verification step. Once all five records propagate — usually within a few hours — mail sent to your custom address arrives in iCloud Mail across all your signed-in Apple devices and at icloud.com.
What iCloud custom domain does not provide: standalone SMTP credentials for a third-party mail host, a full collaboration suite, per-user admin controls, or any calendaring outside Apple's own apps. It routes iCloud Mail through your own address — nothing more, and nothing less.
Before You Start#
Before opening Settings, confirm you have these four things ready. Missing any one of them will stop the process before it finishes.
System requirements: setup works on iPhone or iPad running iOS or iPadOS 15 or later, on Mac running macOS Monterey (12) or later, and at icloud.com on any modern browser. The web path is the most complete option and works regardless of the OS version on your other devices.
- A paid iCloud+ subscription at any storage tier — 50 GB, 200 GB, 2 TB, 6 TB, or 12 TB. The free 5 GB Apple ID plan does not include Custom Email Domain.
- iCloud Mail switched on in your Apple ID settings. It defaults to on for iCloud+ accounts but can be manually disabled.
- A domain already registered with any registrar — GoDaddy, Cloudflare, Namecheap, Squarespace, and most others all work.
- Login access to that registrar's DNS panel with permission to add and edit records.
Not available in all regions
How to Set Up a Custom Email Domain with iCloud+#
- 1
Open iCloud settings
On iPhone or iPad, go to Settings > [your name] > iCloud > iCloud Mail. On Mac, open System Settings > [your name] > iCloud > iCloud Mail. In a browser, go to icloud.com, click the grid icon at the top right, choose Settings, and scroll to Custom Email Domain.
- 2
Select Custom Email Domain
The settings screen shows a Custom Email Domain section. Tap or click it. Apple will ask whether this domain is for you only or for members of your Family Sharing group. Choose carefully — you cannot change this designation later without removing the domain and starting the process over.
- 3
Enter your domain name
Type the domain exactly as it appears at your registrar — for example, yourdomain.com. Do not include www or mail as a prefix. Apple checks that the domain is not already claimed by another Apple ID.
- 4
Choose your email addresses
Apple lets you create up to three addresses per person on the domain. You might use [email protected] and [email protected], for instance. These become iCloud email addresses linked to your Apple ID. You can add more addresses or delete existing ones later from the same settings screen.
- 5
Open your registrar's DNS panel
Keep the iCloud setup screen open. In a separate browser tab, log in to your registrar or DNS host and find the DNS record editor for your domain. You are going to add five records. Do not close the Apple screen — the verification token it displays is tied to your current session.
- 6
Add both MX records
Create two MX records at the root of your domain. Depending on your registrar, the root is entered as @ or left as an empty host field. Both records use priority 10. First record value: mx01.mail.icloud.com. Second record value: mx02.mail.icloud.com. If your domain already has MX records pointing to a previous mail provider, delete those first. Two competing sets of MX records at the same priority will cause delivery failures.
- 7
Add the SPF TXT record
Add a TXT record at the root with the value: v=spf1 include:icloud.com ~all. If your domain already has an SPF record, add include:icloud.com to the existing record instead of creating a second TXT record. Two SPF TXT records at the root break SPF validation for your domain.
- 8
Add the DKIM CNAME record
Apple generates a CNAME record for DKIM signing specific to your domain. The host name for this record is sig1._domainkey, and the value Apple shows you during setup is a long string pointing to Apple's signing infrastructure. Copy it exactly. Some registrars automatically append the root domain to any CNAME host you enter — if yours does, enter only sig1._domainkey rather than sig1._domainkey.yourdomain.com, or the record will resolve to the wrong address.
- 9
Add the verification TXT record
Apple provides a short TXT record whose value begins with apple-domain= followed by a unique token for your account. Add this as a TXT record at the root. This is how Apple confirms you own the domain, not just that you know the domain name.
- 10
Complete verification
Return to the iCloud settings screen and click or tap the button to verify your domain. If propagation is complete, Apple marks the domain active immediately and mail begins routing. If verification fails, wait 30 minutes and try again. DNS propagation typically completes within a few hours but can take up to 48 in worst-case TTL scenarios.
- 11
Import existing email (optional)
If you have mail at another address you want to bring across, go to icloud.com/icloudplus, click Custom Email Domain, select the address, scroll down, and choose Import Mail. The import works only via icloud.com and only from supported providers. Check how much iCloud storage you have before starting — imported messages count against your quota.
Platform Differences at a Glance#
The same setup flow is available from three starting points. The icloud.com path is the most reliable across all device types and OS versions because it has no version requirement beyond a modern browser.
Regardless of where you complete setup, the resulting mail account appears automatically across all your signed-in Apple devices. Mail you receive at your custom address lands in iCloud Mail on iPhone, iPad, Mac, and icloud.com in the same inbox as your @icloud.com address.
| Platform | Access path | Full setup available? | Requirement |
|---|---|---|---|
| iCloud.com | Settings icon > Custom Email Domain | Yes — most complete path | Any modern browser |
| iPhone / iPad | Settings > [Name] > iCloud > iCloud Mail | Yes | iOS or iPadOS 15 or later |
| Mac | System Settings > Apple ID > iCloud > iCloud Mail | Yes | macOS Monterey (12) or later |
| Windows | iCloud for Windows handles sync only | No — use icloud.com for setup | iCloud for Windows plus a browser for setup |
What to Do When Verification Fails#
The most common reason Apple cannot verify a domain is propagation delay. DNS changes can take anywhere from a few minutes to 48 hours to become visible worldwide, depending on the previous TTL value on your records. Before assuming something is configured wrong, check propagation at dnschecker.org and confirm all five records are visible from multiple locations.
If propagation looks complete but Apple still shows an error, work through this list:
- Two SPF TXT records: if you added a new SPF record instead of editing the existing one, you now have two records starting with v=spf1. Delete one and merge the include values into a single record.
- Old MX records still present: if you forgot to remove the previous mail provider's MX records, they compete with Apple's. Remove all non-Apple MX records from the root of the domain.
- DKIM CNAME host doubled: some registrars automatically append the root domain to CNAME host fields. If you entered sig1._domainkey.yourdomain.com and your registrar appended the domain again, the record resolves to the wrong address. Re-enter the host as sig1._domainkey only.
- Whitespace in the verification TXT value: some DNS panels add a space before or after a pasted value. Delete any leading or trailing whitespace from the apple-domain= token.
- Mail arriving in spam after setup: if mail flows but lands in recipients' spam folders, the DKIM CNAME has likely not fully propagated. Wait 24 hours, then ask a test sender to check whether DKIM shows as passing in the email headers.
Verification does not retry automatically
A Faster Way to Handle Everything That Arrives#
Getting your custom domain set up is the start, not the finish. Every email that arrives at your new address still needs to be read, prioritized, and replied to — unless you add a triage layer on top.
AI Emaily connects to iCloud Mail and to any other mailbox you run, whether Gmail, Outlook, or a custom IMAP account. It triages incoming threads, drafts replies in a voice you define through a user-set Context brain and per-client profiles, and routes mail based on rules you control. Nothing sends without your approval unless you explicitly configure it to. We build AI Emaily.
Frequently asked
See it in AI Emaily
Sources

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.