I’m building Millionaire.email, a security-first email service.
And like everyone else, I’ve always heard:
“Proton Mail is the most secure email on the planet.”
So I got curious.
How did Proton get so much hype?
Let me check their security… should take 5 minutes, right?
Yeah. NO.
That was the last peaceful thought I had. 😂
I started checking DNSSEC… DANE… MTA-STS… TLS-RPT… DKIM…
One by one…
And instead of finishing in minutes, I ended up sitting there like:
“Wait… this can’t be right… WHAT?!” 😳
DNSSEC not fully enforced
No ED25519 DKIM
No DANE/TLSA
MTA-STS gaps
TLS-RPT missing in places
I genuinely thought Proton would be flawless.
But I got plot-twisted by reality.
If you want the full technical breakdown (with proof):
👉 https://www.millionaire.email/post/millionaire-email-vs-proton-me-complete-security-architecture-comparison-2025
Not throwing hate — Proton is good.
But as someone building a secure email from scratch, this was a shock + comedy + motivation moment.
And it made my philosophy even stronger:
Don’t trust us. Verify us. 🔐
Top comments (3)
Hi, welcome to DEV!
The security points you mentioned (DNSSEC, DANE, MTA-STS, DKIM choices, etc.) are interesting and definitely worth discussing.
But the post leans quite heavily toward promoting your own email service, which makes the overall tone feel more like marketing than a technical breakdown.
If you expand the analysis with deeper comparisons, data, and neutral explanations, it would fit the DEV community much better.
The topic itself is solid, it just needs a more balanced presentation. 🔐✨
Thanks for the feedback, genuinely appreciate it!
I get what you mean. I’m deep in building an email service myself, so when I checked Proton’s security I kind of wrote from that mindset… and it probably came across more like “my product vs theirs” instead of just a neutral breakdown.
That wasn’t the goal, I was just surprised by what I found and shared it the same way I experienced it.
Your comment helps a lot in understanding how it reads from the outside, so thanks for pointing it out. Always happy to learn and improve how I share things here.
Glad the feedback was helpful, and really appreciate your thoughtful reply. ✨
It’s completely normal for things to read differently when you’re deep in your own product, and it’s great to see the openness you brought to the conversation.
Your findings are valuable on their own, and presenting them with a more neutral structure will make the community engage with them even more.
Exchanges like this keep the space constructive and focused on strong technical content.
Looking forward to seeing the refined version or any future deep dives you publish. Keep building! 🔥🚀