TL;DR
- icloud.com, me.com and mac.com are Apple's own domains, so they are not catch-all.
- Custom domains on iCloud+ have an optional "Allow All" setting. When on, mail to any inactive address goes to the owner's inbox.
- When it is off, Apple says those emails are "returned to the sender". We do not know from Apple's text whether that happens during the SMTP conversation or after.
The direct answer
Apple's iCloud guide describes a catch-all for custom email domains. The owner can turn on "Allow all incoming emails to a custom email domain", after which "any emails that are not sent to an active email address go to the domain owner's inbox". Apple adds that "if this setting is not turned on, those emails are returned to the sender", and that mail to deleted addresses is always returned. Addresses already created for other members of the domain are not redirected to the owner (iCloud User Guide: custom email domain, checked 2026-10-18).
So an iCloud-hosted company domain can be a catch-all, and its owner chose that. A plain icloud.com address cannot, because the setting belongs to custom domains.
How to tell which one you have
Both look like normal domains with Apple's mail servers behind them. The difference is the address: [email protected] is Apple's consumer domain, while [email protected] with iCloud MX records is a custom domain. We find out the same way as for any domain: ask about a random address that cannot exist.
RCPT TO:<[email protected]> → 250 OK
RCPT TO:<[email protected]> → 250 OK (Allow All is on)What you will typically see
The method is the same everywhere: we open an SMTP session with the domain's mail server, ask whether it will take mail for the address, ask the same about a random address that cannot exist, and never send the message (how it works).
| What the server says | Our result |
|---|---|
| Accepts the address, refuses the random test address | deliverable (risky: low_quality for role addresses such as info@) |
Refuses the address (550 5.1.1 or similar) | undeliverable: rejected_email |
| Accepts the address and the random test address | risky: low_deliverability (catch-all) |
Temporary 4xx answer (deferral, rate limit, greylisting) | unknown: unavailable_smtp after a later retry |
For a custom domain with Allow All, every address looks accepted, so the result is risky, not deliverable. That is correct: the mail would go to the owner, who may or may not be the person you want.
What we couldn't confirm
- Whether Apple refuses missing recipients at the SMTP stage or accepts and bounces later. Apple says "returned to the sender" and no more.
- How Apple's servers treat repeated probing. We found no Apple source.
- Our own port-25 connection tests to iCloud's mail servers went through a VPN that blocks port 25, so they say nothing about Apple's behaviour.
Sources
- iCloud User Guide, custom email domain and Allow All: checked 2026-10-18
Common questions
Is iCloud Mail a catch-all?
icloud.com is not. A custom domain on iCloud+ can be, if the owner has turned on Allow All.
What happens to mail for a missing iCloud address?
With Allow All off, Apple says it is returned to the sender. With it on, it goes to the domain owner's inbox.
Can I verify an iCloud address?
Yes, with the usual check. If the domain turns out to accept every address we mark it risky: low_deliverability.