Blog/ Apple Mail & iCloud

iCloud Custom Domain Not Verifying: DNS Fixes That Work

Nafiul HasanNafiul Hasan· 10 min read
AI Emaily blog cover for fixing an iCloud custom email domain stuck unverified, showing corrected DNS records for iCloud MX, verification TXT, SPF and DKIM replacing leftover records from a previous provider

The short answer

An iCloud custom domain stays on Pending when leftover MX records from a previous mail host still exist or the apple-domain verification TXT is not at the root (@). Delete every MX except mx01.mail.icloud.com and mx02.mail.icloud.com, publish the TXT, SPF and DKIM exactly as iCloud shows, wait for DNS, then click Verify.

Domain stuck on Pending? A leftover MX from your old host is the usual cause. Remove it, add the verification TXT at @, add SPF and DKIM, then re-verify.

On this page
  1. 01iCloud MX records and the other DNS records iCloud needs
  2. 02What to do when it still doesn't verify
  3. 03How to fix a domain stuck on Pending, step by step
  4. 04Before you start: what iCloud requires
  5. 05Seeing "existing non-Cloudflare MX records conflict with Email Routing"?
  6. 06When nothing else works: remove and re-add the domain
  7. 07A faster way after the domain verifies

When an iCloud custom domain won't verify, the DNS almost always disagrees with what Apple expects: a record is missing, mistyped, on the wrong host, or an old provider's MX is still there. This is a troubleshooting guide for a domain that is stuck, not a from-scratch setup (that is iCloud custom domain setup from scratch).

iCloud MX records and the other DNS records iCloud needs#

iCloud MX records: mx01.mail.icloud.com and mx02.mail.icloud.com, both at priority 10, and no other MX records on the domain. Apple tells you to delete any existing MX records before adding these. The table lists all five iCloud DNS records, using the example values from Apple's setup article.

The apple-domain string and the DKIM target are generated for your domain, so copy the exact values from the iCloud setup screen rather than from any guide, including this one. Apple's article suggests a TTL of 3600 seconds (1 hour).

RecordTypeHost / nameValue (copy the exact one iCloud shows)
VerificationTXT@ (root)The personal apple-domain=... value iCloud gives you
Mail routingMX@ (root)mx01.mail.icloud.com, priority 10
Mail routing (second)MX@ (root)mx02.mail.icloud.com, priority 10
SPFTXT@ (root)v=spf1 include:icloud.com ~all
DKIMCNAMEsig1._domainkeysig1.dkim.<yourdomain>.at.icloudmailadmin.com

Both MX records use the same priority

iCloud publishes two MX records and Apple's article gives both priority 10. Equal priority is expected, not a mistake to correct. If your setup screen shows different values, use those: Apple's generated values win over any static list.

What to do when it still doesn't verify#

Match your symptom to the table and fix that one cause. The fastest diagnostic is to query your domain's records with a public DNS lookup tool and compare what comes back to what the iCloud screen expects.

SymptomLikely causeFix
Domain stuck on Pending for hours or daysVerification TXT missing, mistyped, or on the wrong hostAdd the apple-domain TXT at the root (@), copied exactly, then re-verify
MX record error, or mail bounces after switchingLeftover MX records from a previous provider are still published alongside iCloud'sDelete every non-iCloud MX record; keep only mx01 and mx02 at priority 10
Verifies, but outgoing mail is marked as spamSPF or DKIM record missing or wrongPublish the SPF TXT and the sig1._domainkey CNAME; merge SPF if one already exists
Records look right but iCloud still won't verifyDNS hasn't updated yet, or a long TTL is still serving the old answerWait out the previous record's TTL, then re-verify (see the timing FAQ)
SPF permanent error, or two SPF records reportedA second v=spf1 record exists from another serviceMerge into one TXT: v=spf1 include:icloud.com include:<other> ~all
Can't set up the domain at allThe registrar has a lock on the domain, or the account doesn't meet Apple's requirementsUnlock the domain at the registrar, and check the requirements below
"Existing non-Cloudflare MX records conflict with Email Routing"This is Cloudflare's error, not iCloud's: Email Routing was switched on while other MX records existSee the Cloudflare section below

Conflicting MX records are the number-one cause

The most common reason a domain won't verify, or verifies but loses mail, is a leftover MX record from a previous provider. Mail only routes correctly to iCloud while iCloud's two MX records are the only ones published. Delete every MX that isn't mx01.mail.icloud.com or mx02.mail.icloud.com, and check for a registrar email-forwarding or parking feature that adds its own MX.

How to fix a domain stuck on Pending, step by step#

Work through these in order at your DNS host, saving each record before starting the next, with the iCloud setup screen open in another tab to copy from.

  1. 1

    Read the exact records iCloud is asking for

    Sign in at icloud.com/icloudplus, open the Custom Email Domain widget and click Manage. iCloud shows the records it expects and the current status. Treat this screen as the source of truth: your apple-domain string and DKIM target are unique to your domain.

  2. 2

    Remove conflicting MX records

    In your registrar's DNS panel, delete every MX record that doesn't point to iCloud: an old Google Workspace set (aspmx.l.google.com and friends), a previous host, or the registrar's default email-forwarding MX. Leave only mx01.mail.icloud.com and mx02.mail.icloud.com, both at priority 10.

  3. 3

    Publish the verification TXT at the root

    Add a TXT record on the root of the domain with the exact apple-domain=... value iCloud shows. In most panels the host is @. Per Apple, if your registrar doesn't accept @, use your domain name as the host instead, and if it rejects quotes or trailing periods, omit them. Don't put the record on a subdomain.

  4. 4

    Add SPF and DKIM

    Add the SPF record as a TXT at the root (v=spf1 include:icloud.com ~all) and the DKIM record as a CNAME at sig1._domainkey pointing to the icloudmailadmin.com target iCloud gives you. If you already publish an SPF record, don't add a second one: add include:icloud.com before the ~all in the existing record. For Cloudflare-specific screens, see how to add SPF and DKIM at Cloudflare.

  5. 5

    Wait for DNS, then re-verify

    Save everything, then click Verify on the iCloud setup page. Apple says saved changes might take a few minutes before they can be verified. If an old record with a long TTL is still being served, it can take longer. When each record checks out, the domain moves from Pending to active.

Copy the values exactly, including punctuation

A single missing character in the apple-domain string or the DKIM target makes that record fail, even though it looks present in your DNS panel. Copy from the iCloud screen, not by retyping.

Before you start: what iCloud requires#

Custom Email Domain is part of iCloud+, so you need an active iCloud+ subscription, two-factor authentication on your Apple Account and a primary iCloud Mail address. Apple notes the feature isn't available in every country or region. You also need to own the domain and be able to edit its DNS at whatever registrar or DNS host manages it, such as GoDaddy, Namecheap, Cloudflare or Squarespace.

Apple can update the records for you at some registrars if you sign in during setup; if yours isn't supported, or that step failed, add every record by hand. If your registrar has a lock on the domain, Apple says you can't set it up with iCloud Mail. Apple's own instructions start from icloud.com/icloudplus, so use a browser for this; the DNS edits themselves always happen at your registrar.

Seeing "existing non-Cloudflare MX records conflict with Email Routing"?#

That message comes from Cloudflare Email Routing, not from iCloud. Cloudflare's documentation lists it as error 2008, "Non-Cloudflare MX records exist". It appears when you turn on Email Routing while another provider's MX records are still on the domain, and iCloud's two MX records count as another provider's.

A domain can't point its MX at both services. Cloudflare says Email Routing requires its own MX records and can't be used with external mail servers on the same domain. So pick one for the domain. If you want iCloud mail on it, don't enable Email Routing and keep iCloud's two MX records. If you want Email Routing, delete iCloud's MX records and enable Email Routing straight after, then create your routing rules immediately: Cloudflare warns that there is a brief window with no MX records, and that mail to an address with no matching rule is rejected. Doing this ends iCloud receiving mail for the domain.

Cloudflare also notes that you can keep another provider's SPF include and its DKIM records, since DKIM selectors use different names, as long as you merge everything into a single SPF record. Cloudflare's docs don't say whether Email Routing can serve a subdomain alongside another provider, so check them before relying on that.

When nothing else works: remove and re-add the domain#

If the records are correct, the conflicts are gone and you've waited out your old TTL but the domain still won't verify, removing it from iCloud and adding it again starts setup fresh. Do this last, not first. Removing the domain can interrupt mail to its addresses and you'll have to re-create each custom address afterward, so note them down, pick a quiet window, and exhaust the record fixes above before you reach for it.

Before-and-after of iCloud custom domain DNS: the before state shows leftover MX records from a previous provider plus a verification TXT on the wrong host; the after state shows only iCloud's two priority-10 MX records, the apple-domain TXT at the root, and SPF and DKIM present
The fix is subtractive as much as additive: remove the old provider's records, then leave iCloud's set clean.

A faster way after the domain verifies#

Setting up iCloud's records is a one-time job that belongs to Apple and your registrar. A mail client can't verify a domain or edit DNS for you, and AI Emaily doesn't try to. We are not a DNS host, and this guide's fixes stand on their own.

The adjacent thing we do starts once the domain is verified and mail flows. AI Emaily connects to your iCloud mailbox over IMAP and becomes the inbox you work in: it triages what lands there and drafts replies from the Personal Context you set, with approve-before-send, undo and an audit trail. It also weighs SPF, DKIM and DMARC results on incoming mail when scoring suspicious senders. It comes with a 7-day free trial on Pro or Autopilot, and a 14-day money-back guarantee.

Frequently asked

Nafiul Hasan

Written by

Nafiul Hasan

Nafiul 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.

EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
More from Nafiul
Ready when you are

Domain verified? Make the inbox behind it work for you.

Connect your iCloud mailbox to AI Emaily to triage and draft replies from the Personal Context you set. Start a 7-day free trial on Pro or Autopilot.

  • 7-day free trial
  • Cancel anytime
  • Every provider