A domain-change headline has left some iCloud+ users wondering whether their hidden addresses will stop working.
Fast answer: As of October 28, 2026, Apple has confirmed that iCloud+ Hide My Email addresses will continue using @icloud.com. Ordinary users do not need to replace an address just because of the announced domain change. Sign in with Apple is a separate feature, so check its update separately.
This guide is for people new to Apple Hide My Email who are choosing an address for a website signup. It also helps iCloud+ users who considered switching after seeing the domain news.
If the account will need ongoing messages, replies, or recovery, the key decision is whether the address will remain under the account holder’s control.
Last updated October 28, 2026. Domain and feature details were checked against Apple’s August 24 developer update and Apple’s current Hide My Email support information. Check those official pages again if Apple publishes a later change.
For readers who saw the earlier announcement
Apple’s earlier developer announcement described a planned change. That older notice is now marked as containing outdated information; it should not be read as the current status. The important distinction is between a plan that was announced and a later official update that changes what users should expect.
In its August 24, 2026 update, Apple confirmed that iCloud+ Hide My Email addresses will continue to use @icloud.com. In practical terms, a user who already has one of these addresses does not need to create a replacement solely because of the earlier domain plan.
That answer is narrower than “nothing can ever go wrong.” It only addresses the domain change. If an address is not receiving messages, check the account’s current forwarding settings and Apple’s instructions for Hide My Email. A domain announcement by itself is not evidence that an individual address has failed.
The old announcement remains useful as background, but not as proof of what is currently planned. Apple’s earlier notice is identified as containing outdated information. Where that notice and the later update differ, use the later official update.
Key distinction: The confirmed decision applies to iCloud+ Hide My Email. It does not mean that every Apple-generated private address uses the same domain or follows the same rollout.
For iCloud+ users worried about an existing address
An existing Hide My Email address does not need to be swapped merely to “get ahead” of the domain news. Changing it without a specific reason can create its own work: the address may already be used by a site, and changing a registration email can involve verifying the new one or updating account records.
Before making any change, identify the actual problem:
- Is the address still listed in the relevant Apple account settings?
- Is the message missing from the destination inbox, or is the website rejecting the address before sending?
- Does the service send to the address but the forwarding destination filter or spam folder catch the message?
- Is the issue limited to one sender, or does it affect mail from different services?
These checks distinguish a domain question from a delivery or account-setting issue. Apple’s current Hide My Email support page and iCloud feature guide explain how the feature works and where to manage it. Use those instructions for account-specific troubleshooting rather than treating a news report as a diagnosis.
An address that forwards messages can be useful for signups that may produce future notices. But it remains tied to the account and forwarding setup behind it. If that account becomes inaccessible, the address may no longer be a reliable way to reach the user. That is why account recovery details and long-term access matter more than the visible domain alone.
For readers mixing up Hide My Email and Sign in with Apple
These features can both keep a personal email address from being shown directly to a service, but they are not interchangeable labels for one address system. Hide My Email is an iCloud+ feature that can create an address for signups and forward incoming mail. Sign in with Apple is an account sign-in option, with its own private email address behavior and management context.
Apple’s Sign in with Apple support information describes that sign-in feature separately. The developer update says new Sign in with Apple addresses are planned to use private.icloud.com, while existing addresses continue working and forwarding mail. That is not the same statement as the iCloud+ Hide My Email confirmation that addresses remain on @icloud.com.
The word “planned” matters. It describes the stated direction, not proof that every account or service has already completed a change. For the rollout status, consult Apple’s latest documentation rather than assuming the domain has changed for every user.
| Option | How it is created | Domain update to check | What it means for a signup |
|---|---|---|---|
| iCloud+ Hide My Email | Created through the Hide My Email feature | Apple confirmed continued use of @icloud.com |
A separate address can forward mail to the user’s inbox |
| Sign in with Apple | Selected when a service offers Apple sign-in | New addresses were announced as planned for private.icloud.com; existing addresses continue working and forwarding |
It is part of an Apple-based sign-in relationship, not simply another name for an iCloud+ address |
| Temporary email | Created through a temporary receiving service, where available | Not governed by Apple’s domain announcement | Better suited to short-term, nonessential signups when ongoing access is not needed |
The table describes the difference in purpose, not a guarantee that a website will accept any particular address. A site may apply its own registration rules. A familiar or Apple-associated domain does not guarantee acceptance, anonymity, or protection from every privacy risk.
For beginners choosing an address for a new website
The right choice depends on what happens after registration. If a site may send order updates, security notices, password-reset links, or messages that need a reply, use an address that will remain available. If the signup is short-lived and has no important account attached, temporary receiving may be enough—provided the site permits it.
| Signup need | Long-term forwarding address | Temporary email |
|---|---|---|
| Receive future notices | Usually a better fit if the forwarding account remains accessible | Poor fit when the address or inbox may no longer be available later |
| Reset a password months later | More suitable when the address remains controlled | Risky if the inbox expires or cannot be revisited |
| Keep a personal address off a signup form | Can separate the signup from the main address while supporting later mail | Can avoid using a long-term address for a short-term registration |
| Reply to the sender | Check the feature’s reply behavior before relying on it | Do not assume a temporary inbox supports replies |
| Register for an important account | Use a durable address and maintain recovery options | Avoid for banking, payment, government, or other accounts where losing access could matter |
No single option is best for every registration. An alias or forwarding address is a better fit when the address needs to last. A temporary email is a limited-use choice, not a substitute for a dependable recovery channel.
A practical rule is simple: if losing future access could lock the account, do not use a short-term inbox. This applies even when the first step is only a verification email. A service may later use the registered address to confirm ownership or recover access.
For people choosing between forwarding and short-term receiving
A forwarding address and a temporary inbox solve different problems. Forwarding is about separating the address shown to a service from the main inbox while keeping a route for later mail. Temporary receiving is about handling a short-lived need without making a long-term address part of that registration.
| Decision factor | Hide My Email or another durable forwarding option | Temporary receiving |
|---|---|---|
| Expected account lifetime | Suitable when the account may be used over time | Suitable only when the account and email need are genuinely short-term |
| Future account recovery | Prefer an address that remains accessible | Avoid if a later reset or ownership check is possible |
| Ongoing notifications | Better when the user wants messages to continue arriving | Not dependable for ongoing notices |
| Need to respond | Confirm how replies work for the chosen forwarding service | Confirm capability before relying on it; do not assume replies are supported |
| Privacy expectation | Hides the personal address from the signup, but does not make the user anonymous | Limits use of a long-term address, but does not remove all privacy or account risks |
Apple’s domain decision does not establish whether a site accepts Hide My Email, Sign in with Apple, or temporary addresses. Nor does the domain alone reveal how a site handles stored account data. If a registration form rejects an address, use an allowed, durable alternative for an account that matters; do not assume changing the address domain will solve the site’s policy.
For readers who want to compare these patterns more broadly, ZipFwd’s guide to temporary email versus email aliases explains when each type is a better fit. For signup-specific risks, see the guide to email safety when creating an account.
For anyone checking a temporary inbox before use
Do not infer a service’s capabilities from the category name. A “temporary email” service might provide a receiving inbox, but features such as custom address prefixes, forwarding to a main inbox, address lifetime, message retention, available domains, and registration requirements vary. Those details should be checked on the service’s own current pages before using it.
The same caution applies to delivery expectations. A test with one website cannot establish that every sender will deliver to the same address or that a site will accept it. Sender policies, verification systems, and individual site rules can differ. No Apple announcement can validate a separate service’s delivery behavior.
Before using a short-term address, work through these steps:
- Classify the account. Decide whether it is a disposable registration or an account that could hold purchases, personal records, or access to other services.
- Check the recovery path. If the account may need a password reset or ownership check later, choose an address that will stay under the user’s control.
- Read the service’s current feature details. Confirm whether it receives mail, whether it offers forwarding or custom prefixes, and whether using it requires an account. Do not assume any of these features.
- Review privacy information. Look for clear statements about inbox visibility, message handling, and retention. A hidden address is not automatically an anonymous or private inbox.
- Check the target site’s rules. Use an address type the site accepts. Do not use temporary receiving to bypass a restriction or to register for an account that needs reliable recovery.
- Keep the confirmation route available. If a verification message arrives, make sure the account will not depend on an inbox that is about to become inaccessible.
- Reassess if the account becomes important. If a one-off registration turns into a service used regularly, update the account to an address that can be kept and recovered.
The third step is where product claims need the most care. ZipFwd’s current pages should be checked directly for the functions actually offered, including whether temporary receiving, forwarding, custom prefixes, or registration requirements are available. If a capability is not confirmed on the live product page, do not rely on it. Likewise, no delivery speed, address lifetime, or message-retention period should be assumed without a current, verifiable statement.
A durable address also has limits. It may keep future mail reachable, but it does not guarantee that every service will accept it, that every message will land in the inbox, or that the account holder can reply through it. When those details matter, confirm them before using the address as the only recovery route.
What to do now
For an existing iCloud+ Hide My Email address, no domain-driven replacement is needed based on Apple’s confirmed update. For Sign in with Apple, treat the private.icloud.com announcement as a separate planned update and use current Apple documentation to check rollout details. For a new signup, decide first whether the account needs ongoing messages, replies, or recovery; that requirement determines whether a durable forwarding address or temporary receiving is appropriate.
Temporary email can be a reasonable option for a permitted, short-term signup that does not hold important access. It is not the right choice for banking, payment, government, or any account that depends on long-term recovery. Before trying ZipFwd for a short-lived signup, check its current pages for the features and limits that matter. If future notices or account recovery may be needed, use a long-term address the account holder can continue to control.