Apple gives Hide My Email a label that says 'block me'

For years a Hide My Email alias looked exactly like a normal iCloud mailbox, so banning it meant banning real paying customers. Apple is about to print the difference right in the domain.

In brief

Both Sign in with Apple and Hide My Email aliases are moving to @private.icloud.com. One regex now separates relay addresses from real iCloud mail, and a site can reject all of them in a single rule.

The author's escape hatch: generate spare @icloud.com aliases now, before the change lands, at a rate limit of at least 30 per hour.

The catch surfaced in the thread: ban the new domain and you also break the Apple sign-in button you were told to add.

A privacy feature that worked because it was invisible

Hide My Email's quiet superpower was plausible deniability. An alias arrived as [email protected], indistinguishable from a paying iCloud user, so any site that blocked it risked blocking real customers too. That cost is what kept the feature usable.

The author's post lays out the change announced June 15, 2026: both Sign in with Apple and Hide My Email aliases are migrating to the @private.icloud.com subdomain. He calls it "a big hit for iCloud privacy." The mechanics are simple and that is the problem. A service no longer has to guess which addresses are relays; it can reject everything from one subdomain in a single rule, the same way it already blocks throwaway-email providers. His recommended hedge: pre-generate spare @icloud.com aliases now, while the old domain still works, at a rate limit he puts at "at least 30 per hour."

"What am I missing?" — the question that exposed the trick

Not everyone saw the threat immediately. The top voice in the thread asked the obvious question:

"Could someone clarify why having Sign in with Apple and Hide My Email on the same domain would make a blanket ban easier rather than harder? What am I missing?" — a product designer

The answer is separation, not combination: the new subdomain peels relay traffic away from ordinary @icloud.com mail, so blocking it no longer hits genuine mailboxes. One longtime user logged the loss in concrete terms:

"It's actually useful compared to Gmail's useless 'yourrealaddress+alias' that gives away your actual email anyway, and it helped me catch quite a few spammers/data sellers." — a developer who uses aliases to trap data sellers

The self-defeating ban

The sharpest counter cut against the alarm. Banning the relay domain isn't free for the site either:

"Okay but banning private relay emails would also mean your site is blocking Apple sign in?" — a commenter who likes computers

And another noted Apple's App Store rules may already forbid it: apps are required to support Sign in with Apple, so breaking it could get an app pulled. The rule that emerges is narrower than the headline: a site can now cheaply reject Hide My Email at signup, but only by accepting the same friction it was told to avoid. The privacy guarantee didn't vanish; Apple just moved it from "impossible to target" to "costly to target," and handed the bill to whoever clicks block.

Get breakdowns like this every day

The top Hacker News stories, unpacked — by email, Telegram, or RSS.

Next story · 10 of 23 Read more
🚀Tech

GrapheneOS hits Android 17, but only if you bought the right Pixel

The Android 17 port is already running on seven Pixel models. The recurring complaint in the thread isn't about the OS at all: it's that you still have to buy Google hardware to escape Google.

★ 397 · 💬 159 · discuss.grapheneos.org · 2 min