About this video

File verification needs a paid account. BillionVerify is not affiliated with or endorsed by Apple.

Video transcript

1. 00:00What you're seeing

   Your iCloud addresses came back unknown. Not valid, and not invalid. Here's what that result means, and what to do with those contacts. Three Apple domains behave this way. icloud.com. me.com. And mac.com. Each one returns the status unknown, with the reason smtp_unverifiable. Unknown makes no claim against the address. It may well be a working inbox. We just have no evidence either way.

2. 00:29Why it happens

   Most mail servers give a usable reply when you name a recipient. On these three domains, Apple's servers don't give a signal we can rely on. So any verdict built on that reply would be a guess. So we don't ask. The check runs through syntax, disposable, labels and DNS, then stops at the policy layer. No SMTP connection is made for these addresses. Earlier layers can still decide. A broken address format is invalid, even on iCloud. A personal name is unknown. So is a role name, like info, because the check stops before role can take over.

3. 01:03Where to find the reason

   In the console, a single check shows Unknown Status. The reason code isn't on that card. To see it, open the live results on a file job, download the results file, or read the API response. In a results file, filter on ev_status and ev_reason, then look at ev_domain. You need all three, because this reason code can appear on other domains, for other causes. Verifying these addresses again won't change anything. The API marks this reason as not retryable. There's no setting for it, and passing check_smtp: true doesn't help, because the policy layer comes first. You don't pay for these results. An unknown never uses a credit, however many iCloud addresses sit in your file. One exception matters. This rule covers Apple's own domains. A custom domain that forwards to iCloud gets a normal SMTP check, so it can come back with a definite result.

4. 01:55What to do with them

   So what do you do with them? Our help center's advice is to treat them as unconfirmed, but likely fine to send. Don't delete them just because they say unknown. Keep them in your send, and let real mail answer the question. If nothing bounces, keep mailing that contact. If it hard bounces, remove the address. Anything with a broken format comes out before you start. That's the safest way to confirm an iCloud address. A normal send, with your bounce reports open. Then update your list from what actually happened. Check the domain. Check the reason. Keep the address, and let your bounces settle it.

5. 02:32Get started free

   20 free credits every day you use your account, up to 600 a month. No credit card required. Start at billionverify.com.

Featured in this video