Compare the whole suffix with Apple’s current announcement
Apple’s August 2026 developer update introduces private.icloud.com for new Sign in with Apple addresses later in the year. It also says existing privaterelay.appleid.com addresses continue forwarding. Its October support article recognises both domains. These are email-address domains; they are not a request to visit an unrelated sign-in website. Keep using the app or account page you intended to open.
Record a validation error without changing account identity
Suppose a viewing app accepts your Apple sign-in but its contact form marks the displayed relay address invalid. Copy the exact error and identify whether the rejection happens before submission. Avoid replacing the address with a guessed older-domain version: that creates a different destination. If support needs the account identifier, provide it privately through the established channel rather than publishing a screenshot containing the full address.
The service may need a form update
Apple instructs developers to accept the new domain alongside the old one in account systems, validation and allowlists. A site operator should check those rules and the account-recovery flow together. Test sign-in and recovery-message delivery after correcting a validator, retaining the existing account. The same announcement says iCloud+ Hide My Email addresses remain on icloud.com; it does not migrate every Apple-related address to the new suffix. A corrected form should preserve the customer’s existing account rather than creating a second profile.
Questions, answered
Should I replace private.icloud.com with the older suffix myself?
No. Use the actual relay address shown in your Apple settings; changing its domain invents a different address.