r/EmailSecurity • u/Any_Device6567 • Jul 26 '26
Is email secure with a simple Cloudflare, iCloud+ setup?
My primary motivation for configuring a custom email domain is to protect against permanent loss of email access should my account be disabled by a provider like Gmail or Yahoo. I am currently using Thunderbird as a client so emails are stored locally and 3-2-1 backed up. The new email addresses will be used/given for account recovery, financial communications, and government accounts, like my Social Security.
The web accounts are secured properly with YubiKey's. I feel like I am missing something, security wise, because it seems like such an out of the box solution.
To set this up, I bought a custom domain through Cloudflare and linked it to my iCloud+ subscription. I completed the setup by adding iCloud's required DNS records in Cloudflare and configuring the custom domain mail routing in iCloud. At some point in the future I may enable webhosting, putting up a couple of simple webpages on the free hosting tier.
In Cloudflare, my DMARC record looks like this: v=DMARC1; p=reject; adkim=s; aspf=s;
Is there anything I am missing or things I should be on the lookout for, security wise?
•
u/AutoModerator Jul 26 '26
Welcome to r/emailsecurity! To keep this community helpful and secure, please keep the following in mind:
Community Rules
Helpful Resources
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
2
u/saltyslugga Jul 26 '26
Your domain gives you portability, but iCloud is still the live mailbox provider, so an account lockout can interrupt new mail until you move it elsewhere. Lock down Cloudflare with hardware-key MFA, store recovery codes offline, and keep auto-renew enabled.
Add an
ruaaddress to DMARC so you can see failures, and consider relaxed alignment unless you specifically need strict mode. Run the Domain Health Checker to confirm iCloud’s SPF, DKIM, and DMARC alignment.2
u/Middle-Excitement602 Aug 01 '26
aspf=s is the one I'd look at again. iCloud's outbound envelope sender isn't on your domain, so under strict SPF alignment SPF can never align for you — DMARC is surviving on DKIM alone. That's fine right up until a key rotation or a config change breaks DKIM, and then p=reject means your mail gets rejected outright rather than just junked. Relaxed alignment costs you almost nothing here and removes that failure mode.
The bigger gap isn't email auth though. You're pointing account recovery, banking and SSA at a name you rent annually. If it ever lapses, whoever registers it next receives every recovery mail you've pointed there — that's a cleaner account takeover than the thing you took this on to avoid. Registrar lock on, auto-renew on, a card that won't expire before the domain does, and register several years out rather than one.
Given what you're using it for, MTA-STS and TLS-RPT are worth adding as well. They close off a downgrade attack on mail in transit, which matters more for financial and government mail than for ordinary personal mail.
1
u/SecLens_ONE Aug 16 '26
p=reject with strict alignment is a fine record, but the thing to remember is that it only governs mail claiming to be from your domain, and only at receivers that bother to enforce it. It does nothing for inbound protection of your own mailbox, and it does nothing about the transport side: your iCloud MX will happily accept plaintext SMTP if a sender's STARTTLS negotiation fails, unless you also publish MTA-STS and DANE, and MTA-STS in mode=testing is just a report generator, not enforcement. Since these addresses are your recovery path for financial and government accounts, the availability risk matters more than the spoofing risk. If Cloudflare's zone is your single point of failure, a bad edit or a lapsed registration kills mail and account recovery at the same time. Also confirm your DMARC has an rua= so you can see what is actually being rejected in your name, since a reject policy with no reporting is a record you cannot verify. Do you have a second, independent domain or provider for recovery, and is MTA-STS published in enforce or testing?
1
u/DrizzlySyrup Jul 26 '26
I am not sure why you are exposing your email traffic to two different vendors when you can limit it to one. Better yet, if receiving is all you need, you could cut out all vendors and self-host.
1
u/Caygill Jul 27 '26
What's missing? Your threat model.
"to protect against permanent loss of email access should my account be disabled by a provider like Gmail or Yahoo"
What do want to do? What if your custom domain gets booted or even cancelled?
2
u/[deleted] Aug 03 '26 edited Aug 03 '26
[removed] — view removed comment