ChatGPT answers, unedited

For a health-focused blog, I’d use Proton Mail with your own domain rather than self-hosting mail. It supports custom domains, zero-access encryption, E2EE between Proton users, and password-protected encrypted mail for outside recipients. Proton Proton Proton

• Use contact@yourdomain.com for the blog.
• Enable SPF, DKIM, and DMARC.
• Never put sensitive health information in ordinary email; use Proton’s encrypted/password-protected messaging when appropriate.
• If maximum encryption coverage—including subject lines—is your priority, Tuta is an alternative. tuta.com

If by “own” you specifically mean running the mail server yourself, say so—I’d recommend a different architecture.

Recommendation: Proton Mail with your own domain. It supports custom domains, end-to-end encryption between Proton users, zero-access encrypted storage, and password-protected encrypted messages to outside recipients. Proton Proton

For a health-focused blog, I’d use:

• contact@yourdomain.com for public inquiries.
• Proton’s encrypted mail for sensitive correspondence.
• SPF, DKIM, and DMARC configured on the domain. Proton
• Do not treat ordinary email as HIPAA-compliant merely because it is encrypted; avoid collecting identifiable patient information unless you have specifically established the required compliance controls.

If maximum encryption—including subject lines—is more important than interoperability, Tuta is another strong option. tuta.com

For a health-focused blog, I’d choose a privacy-first hosted email service rather than running your own mail server. Self-hosting gives you control, but maintaining deliverability, spam filtering, backups, encryption, and security is considerably harder.

My recommendation: Tuta Mail

Tuta is probably the best fit if privacy and encryption are the priorities.

• Your own domain: You can use addresses such as hello@yourblog.com; paid plans support custom domains and aliases. Tuta Tuta
• Strong encryption: Tuta encrypts email content, attachments, subject lines, contacts, and calendars, with encryption keys designed to remain under your control. Tuta
• Post-quantum cryptography: Tuta currently uses X25519 and Kyber-1024 alongside AES-256 for its encryption architecture. Tuta
• Privacy-oriented infrastructure: Its servers are in Germany, and Tuta says its clients are open source. Tuta Tuta
• Good for a blog: You can create separate addresses such as hello@, contact@, privacy@, and editor@ without exposing your personal mailbox.
• External recipients: You can send password-protected encrypted messages to people who don't use Tuta. Tuta

tuta.com

Strong alternative: Proton Mail

Proton would be my second choice—and arguably the better choice if you value compatibility and a mature business-email ecosystem over maximum encryption coverage.

Proton supports custom domains on paid plans, E2EE between Proton users, zero-access encryption for stored incoming mail, and SPF/DKIM/DMARC configuration for your domain. Proton Proton Proton

proton.me

How I'd set it up

For a health blog, I'd use:

Domain registrar → privacy-focused DNS → Tuta/Proton → separate public aliases

For example:

• hello@yourdomain.com — general correspondence
• contact@yourdomain.com — reader messages
• privacy@yourdomain.com — privacy/data requests
• press@yourdomain.com — media
• newsletter@yourdomain.com — newsletter
• admin@yourdomain.com — never publish this address

Then configure SPF + DKIM + DMARC. These aren't encryption, but they're important for preventing someone else from spoofing your domain and for keeping legitimate messages out of spam. Proton specifically recommends all three for custom domains, and Tuta supports them as well. Tuta Proton

One important health/privacy caveat

If readers might send you medical records, diagnoses, prescriptions, or other identifiable health information, don't assume that "encrypted email" automatically makes your setup HIPAA-compliant or otherwise legally compliant. The safest design for a blog is generally not to collect sensitive health information through ordinary email at all. Put a clear notice on the contact page asking readers not to send medical records or other sensitive health information.

Bottom line: I'd pick Tuta + your own domain for the strongest privacy/encryption-oriented setup. Pick Proton Mail if you want a somewhat more conventional professional-email experience while retaining very strong privacy protections.

For a health-focused blog, I’d choose Tuta Mail with your own domain if privacy and encryption are the top priorities.

Recommended setup

• Email: tuta.com
• Domain: Register something like yourblog.com with a privacy-conscious registrar.
• Addresses: hello@yourblog.com, contact@yourblog.com, and separate aliases for newsletters/forms.
• Encryption: Tuta stores mailboxes end-to-end encrypted and encrypts subjects and attachments as well as message contents. It also supports encrypted messages to people outside Tuta using a shared password. Tuta Tuta
• Custom domain: Paid Tuta plans support custom domains, catch-all, and unlimited domain aliases. Tuta Tuta
• Authentication: Configure SPF, DKIM, and DMARC for the domain to reduce spoofing and phishing. Tuta supports all three. Tuta
• Account security: Enable 2FA, preferably with a hardware security key where practical. Tuta supports TOTP and U2F. Tuta

Why Tuta over the alternatives?

Proton Mail would be my second choice. It supports custom domains on paid plans and provides strong encryption, including automatic E2EE between Proton users. Proton Proton Proton is particularly attractive if you want better interoperability with conventional desktop clients through Proton Mail Bridge. Proton

Tuta gets the edge for this particular use case because it encrypts substantially more mailbox data by default, including subject lines and contacts, and its clients are open source. Tuta Tuta

One important caveat: email isn't automatically end-to-end encrypted merely because you use a privacy-focused provider. Messages to ordinary Gmail/Outlook/etc. recipients generally aren't E2EE unless you use the provider's special encrypted-message mechanism. For a health blog, I'd avoid asking readers to send sensitive medical information by ordinary email at all.

My practical architecture:
Your domain → Tuta Mail → SPF + DKIM + DMARC + 2FA → aliases for public-facing addresses

If the blog will collect health information, patient stories, or other sensitive submissions, I'd use a dedicated encrypted submission/contact system rather than making email the intake mechanism.

For a health-focused blog, I’d prioritize privacy, encryption, and operational simplicity—but also remember that ordinary email is not automatically end-to-end encrypted just because your mail server uses TLS.

My recommendation: Proton Mail with your own domain

Proton is the option I’d choose if you want strong privacy without becoming your own mail administrator.

You can use addresses such as hello@yourblog.com while keeping the mailbox on Proton. Proton says mail stored in its system uses zero-access encryption, and messages between Proton users are end-to-end encrypted by default. It also supports OpenPGP and password-protected encrypted messages for recipients who don't use Proton. Proton Proton

proton.me

Why it fits a health-focused publication

• Custom domain: Your readers see contact@yourdomain.com, not a Proton address.
• Strong encryption at rest: Proton uses zero-access encryption for mailbox contents. Proton
• E2EE: Particularly useful when communicating with sources or contributors who also use Proton/PGP.
• Encrypted messages to ordinary email users: Proton's password-protected email feature can provide E2EE even when the recipient doesn't use Proton. Proton
• Hardware-key 2FA: Proton supports FIDO2/U2F security keys, which I'd strongly recommend for the administrator account. Proton
• Less operational risk: You don't have to maintain an exposed SMTP server, spam filtering, backups, TLS configuration, and IP reputation yourself.

One important caveat: email to Gmail/Outlook/etc. isn't automatically end-to-end encrypted. TLS protects the connection, but the recipient's provider can generally access the message. For genuinely sensitive health information, use PGP/E2EE or an encrypted portal rather than ordinary email. Proton

If you specifically mean self-hosted

Then I'd look at Stalwart Mail Server first, with mailcow as the more mature all-in-one alternative.

Privacy Guides currently recommends Stalwart for self-hosting and notes its PGP implementation can provide encrypted message storage and, with WKD plus a compatible client such as Thunderbird, straightforward PGP interoperability with Proton users. Privacy Guides

Mailcow is easier if you want an integrated stack: webmail, DKIM, spam/antivirus filtering, ActiveSync, administration, and 2FA are included. Its documentation also supports SPF/DKIM/DMARC configuration and encrypted mail storage. Mailcow Documentation Mailcow Documentation

The downside is you become responsible for security: server patching, backups, intrusion protection, DNS, IP reputation, spam handling, and deliverability. Self-hosted email is much more work than self-hosting a blog.

A good architecture

For your use case, I'd set it up roughly as:

Blog: your existing web host
↓
Domain DNS: reputable DNS provider with DNSSEC
↓
Email: Proton Mail using your custom domain
↓
Sensitive correspondence: Proton E2EE / OpenPGP / encrypted contact portal
↓
Authentication: hardware security key + strong recovery strategy

And configure SPF, DKIM, and DMARC with a restrictive DMARC policy once you've verified legitimate senders. These are important for preventing spoofing and improving deliverability. Mailcow Documentation

Bottom line: For a small health-focused blog, I'd choose Proton Mail + your own domain rather than self-hosting. If you're deliberately trying to retain complete infrastructure control and are comfortable administering Linux mail servers, Stalwart is the self-hosted privacy-oriented choice I'd investigate first.

For a health-focused blog, I’d prioritize privacy, strong encryption, custom-domain support, and low administrative overhead rather than running your own mail server from scratch.

My recommendation: Proton Mail

Proton Mail is probably the best fit if your blog may receive sensitive health-related messages from readers.

• Custom domain: Paid Proton plans support addresses such as contact@yourblog.com. Proton
• Encryption: Proton uses end-to-end encryption between Proton users, and incoming mail is stored using zero-access encryption. Proton
• Privacy-oriented: Proton's design minimizes its ability to read stored mailbox contents.
• Good fit for a public blog: You can have separate addresses such as contact@, editor@, and privacy@ without exposing your personal address.
• Less maintenance: You don't have to operate and secure your own SMTP server, deal with IP reputation, spam blacklists, patching, backups, etc.

proton.me

An excellent alternative: mailbox.org

I'd choose mailbox.org if open standards such as PGP/S/MIME and European hosting are particularly important to you. It supports custom domains and offers TLS, PGP and S/MIME encryption. mailbox mailbox

It also supports DNS-based OpenPGP key discovery for your custom domain. Mailbox Knowledge Base

mailbox.org

What I'd configure

For a health-focused site, I'd use:

• contact@yourdomain.com — general reader contact
• privacy@yourdomain.com — privacy/data requests
• editor@yourdomain.com — editorial correspondence
• A separate personal/admin address that isn't published
• 2FA on every mailbox/admin account
• SPF, DKIM and DMARC on the domain
• TLS for normal mail transport
• PGP/E2EE when exchanging genuinely sensitive information

One important caveat: ordinary email is not automatically end-to-end encrypted just because your provider uses encryption. If a reader sends you sensitive medical information from Gmail, for example, you shouldn't promise them that the message is end-to-end encrypted. Proton specifically distinguishes E2EE from its zero-access encryption for externally received mail. Proton

If the blog will actually collect, store, or process identifiable patient/health information, that's a different—and considerably more demanding—privacy/compliance question. In that situation, I'd design the contact workflow so the blog doesn't collect health information by email in the first place, rather than treating encrypted email as a complete compliance solution.

Bottom line: I'd pick Proton Mail + your own domain for the simplest strong-privacy setup; mailbox.org is my alternative if PGP/S/MIME and European privacy infrastructure are higher priorities.

For a health-focused blog, I’d prioritize privacy, strong encryption, custom-domain support, and good deliverability rather than literally running a mail server yourself. Self-hosting SMTP can be surprisingly difficult to secure and maintain.

My recommendation: Tuta Mail + your domain

Tuta is probably the best fit if privacy and encryption are your top priorities.

• Use your own domain: e.g. hello@yourhealthblog.com. Paid Tuta plans support custom domains and catch-all addresses. Tuta Tuta
• End-to-end encryption by default: Tuta encrypts emails, attachments, contacts and calendars, and uses modern post-quantum-resistant cryptography. Tuta Tuta
• Good for sensitive communications: particularly useful if readers might contact you about health experiences.
• German hosting/privacy framework: Tuta says its data is stored on its own servers in Germany and protected under GDPR. Tuta
• Open-source clients: Tuta's clients are open source, which is a useful transparency advantage for a privacy-oriented project. Tuta

One important caveat: email to ordinary Gmail/Outlook/etc. recipients isn't magically end-to-end encrypted. For external recipients, Tuta can use password-protected encrypted messages, but the recipient needs to use that mechanism. Tuta

Strong alternative: Proton Mail

Proton is my second choice, particularly if you want a polished ecosystem and interoperability with conventional mail clients.

Proton supports your own domain on paid plans and provides E2EE between Proton users, while incoming external mail receives zero-access encryption. Proton Proton It also supports SPF, DKIM and DMARC configuration for your domain, which is important for protecting your blog from spoofing and improving deliverability. Proton

Another good option: mailbox.org

mailbox is especially interesting if you want traditional email standards plus PGP/S/MIME rather than Tuta's more integrated encryption model.

It supports custom domains, TLS, PGP and S/MIME, with infrastructure in Germany. mailbox mailbox Its PGP implementation can also keep the private key encrypted with a password that isn't stored by mailbox. Mailbox Knowledge Base

How I'd set up your blog

I'd use this architecture:

Domain registrar/DNS → Tuta Mail → hello@, contact@, privacy@

Then configure:

1. Custom domain — yourblog.com
2. Separate addresses/aliases - hello@ — general correspondence
3. contact@ — reader questions
4. privacy@ — privacy/data requests
5. newsletter@ — newsletter infrastructure
6. SPF + DKIM + DMARC — particularly important for preventing someone from impersonating your health blog. Proton
7. MFA/passkeys on the mail account.
8. Don't put health information in ordinary email unnecessarily. Put a prominent notice on the contact page saying that email isn't appropriate for urgent medical information or highly sensitive medical records.
9. Keep newsletter sending separate from your personal correspondence if you're building a mailing list. This protects your primary mailbox's reputation and limits exposure if the newsletter system is compromised.

Bottom line

I'd choose Tuta if the central requirement is "I want the most privacy/encryption-oriented setup that still lets me use my own domain."
I'd choose Proton if you want a slightly more conventional ecosystem and client compatibility.
I'd choose mailbox.org if PGP/S/MIME and conventional email interoperability are particularly important.

For a health blog, I would not self-host the mail server unless you specifically need server-level control and have the expertise to maintain it. A privacy-focused provider gives you considerably less operational risk while still letting your public identity be you@yourdomain.com.

It supports custom domains, TLS, PGP and S/MIME, with infrastructure in Germany. Its PGP implementation can also keep the private key encrypted with a password that isn't stored by mailbox.

For a health-focused blog, I’d prioritize privacy, reliable deliverability, and minimizing the amount of sensitive mail data you personally have to administer.

My recommendation: Proton Mail + your domain

Proton is my first choice if by “host email on my own domain” you mean use addresses such as hello@yourhealthblog.com, rather than literally operating the mail server yourself.

Proton supports custom domains on paid plans, including sending and receiving mail under your own domain. Proton Proton

The privacy advantages are particularly relevant for a health site:

• End-to-end encryption for messages between Proton users.
• Zero-access encryption for mail arriving from conventional email providers, meaning Proton says the stored message contents aren't accessible to it in ordinary circumstances. Proton
• Password-protected encrypted emails can be used when communicating with people outside Proton. Proton
• Your domain can have proper SPF, DKIM and DMARC authentication, reducing spoofing and improving deliverability. Proton
• You don't have to maintain an internet-facing mail server, spam filter, backups, TLS configuration, IP reputation, etc.

Important health/privacy caveat

Don't treat email as automatically HIPAA-compliant just because it is encrypted. If your blog will receive patient information, clinical information, or other regulated health data, I'd design the site so that visitors are not asked to submit sensitive information by ordinary email. Use a purpose-built secure intake system instead, and obtain appropriate legal/compliance advice.

For ordinary blog communications—newsletter administration, reader questions, business inquiries, etc.—Proton is a very good privacy-oriented choice.

If you literally want to self-host the mail server

Then I'd use mailcow on a dedicated VPS.

mailcow bundles Postfix, Dovecot/SOGo, Rspamd, DKIM management, spam filtering, TLS, and other components into a Docker-based mail platform. Mailcow Documentation

A hardened setup would look roughly like:

yourdomain.com → DNS → mail.yourdomain.com → mailcow VPS

with:

• TLS 1.2/1.3 for IMAP/SMTP/webmail
• Let's Encrypt certificates
• SPF + DKIM + DMARC
• MTA-STS to require TLS where supported
• DANE/TLSA + DNSSEC if your DNS/VPS setup supports it
• encrypted server backups
• separate admin credentials + MFA
• firewall restricting unnecessary ports
• monitoring and external outage notifications

mailcow currently supports MTA-STS directly, and its Postfix configuration supports DANE/TLSA policies. Mailcow Documentation Mailcow Documentation It also provides standard encrypted IMAPS/SMTPS connections and STARTTLS. Mailcow Documentation

The downside is substantial: you become the mail administrator. A misconfigured server can leak mail, get blacklisted, lose messages, or become a security liability. Self-hosting also doesn't magically provide end-to-end encryption when emailing Gmail, Outlook, etc.

What I'd choose

For your particular use case, I'd choose Proton with your domain, then configure SPF, DKIM and DMARC and keep the blog's contact form deliberately free of requests for medical/patient information. That gives you strong privacy without taking on the considerable security burden of running your own mail server. Proton

If you want, I can also give you a privacy-hardened setup for yourdomain.com (DNS records, aliases, encryption, backups, newsletter, and a safe health-blog contact form).

For a health-focused blog, I’d prioritize:

• Custom domain support (you@yourblog.com)
• Strong encryption at rest and ideally end-to-end encryption (E2EE)
• Minimal tracking/data collection
• Good account security (2FA/passkeys)
• Reliable deliverability (important for newsletters and reader contact)
• Ability to separate public contact email from private admin email

A good setup is:

Recommended solution: Proton Mail + your own domain

proton.me is my top recommendation for this use case.

Why it fits a health blog:

• Supports custom domains so you can use addresses like: - hello@yourhealthblog.com
• contact@yourhealthblog.com
• privacy@yourhealthblog.com
• Uses end-to-end encryption between Proton users and zero-access encryption for stored mail. Proton
• Has strong privacy positioning and is based in Switzerland. Proton
• Supports security features like 2FA and encrypted ecosystem tools.
• Lets you publish a professional email address without tying your blog identity to a mainstream advertising email provider.

For a health blog, I’d create separate addresses:

Keep your private admin address off the website to reduce spam and phishing risk.

Alternative: Tuta Mail (maximum privacy approach)

tuta.com is worth considering if you care more about privacy than compatibility.

Strengths:

• End-to-end encrypted mailbox, calendar, and contacts. Tuta
• Encrypts more metadata than many traditional email systems, including subject lines. Tuta
• Supports custom domains on paid plans. Tuta

Tradeoffs:

• Less compatible with traditional email clients because it does not use normal IMAP access. Tuta
• Some newsletter and business workflows may require adjustments.

Alternative: Fastmail (best usability)

fastmail.com is excellent if you want a Gmail-like experience.

Strengths:

• Excellent custom-domain email hosting.
• Strong security practices, including encryption in transit/at rest and 2FA support. Fastmail
• Works well with normal email apps.

Tradeoff:

• It is not designed around provider-resistant end-to-end encryption like Proton or Tuta. Fastmail Privacy Ranker

My suggested stack for your blog

Domain registrar

• Choose a privacy-friendly registrar that supports WHOIS privacy.

Email

• Proton Mail with your custom domain.

DNS security
Configure:

• SPF
• DKIM
• DMARC

These help prevent spoofing and improve deliverability. Proton’s custom-domain setup includes guidance for these records. Proton

Website contact form
Avoid sending health-related messages directly into an ordinary website database. Instead:

• Use a privacy-conscious form provider, or
• Route form submissions into your encrypted mailbox
• Add a note telling readers not to submit personal medical details unless appropriate

Important health-content note

Email encryption protects your mailbox, but ordinary email is still not equivalent to a secure patient portal. If readers might send symptoms, diagnoses, test results, or other sensitive health information, consider using a dedicated secure intake system rather than regular email.

For most health blogs (education, wellness, nutrition, fitness, public information), I’d choose:

1. Proton Mail + custom domain — best overall
2. Tuta — strongest privacy posture
3. Fastmail — easiest everyday workflow

I would not self-host email unless you already have strong server administration experience; maintaining spam reputation, patching, backups, and mail security is a significant ongoing task.

For a health-focused blog, I would prioritize:

1. Privacy of reader communications (contact forms, reader questions, newsletter replies)
2. Strong encryption at rest and in transit
3. Custom domain support (you@yourblog.com)
4. Good anti-phishing protections (SPF, DKIM, DMARC)
5. A provider with a clear privacy model (especially important if readers may share sensitive health-related information)

A good solution is usually not running your own mail server. Self-hosting email sounds appealing, but it is difficult to secure, maintain reputation with Gmail/Outlook, and avoid leaks from misconfiguration. A privacy-focused hosted provider is often safer.

Recommended setup: Proton Mail + your custom domain

proton.me

Best overall choice for a health blog.

Why:

• Supports custom domains (for example contact@yourdomain.com). Proton
• Uses end-to-end encryption between Proton users and zero-access encryption for stored mail. Proton
• Supports OpenPGP workflows if you communicate with technically advanced users or organizations. Proton
• Includes strong security features such as 2FA and privacy-focused account protections.
• Has a more conventional email experience than some encrypted providers, including optional desktop-client support through Proton Mail Bridge. Proton

Suggested addresses:

• hello@yourdomain.com — general inquiries
• privacy@yourdomain.com — privacy-related questions
• newsletter@yourdomain.com — mailing list
• press@yourdomain.com — media requests

Alternative: Tuta Mail

tuta.com

A strong option if maximum encryption coverage matters more than compatibility.

Advantages:

• End-to-end encrypts mailboxes and additional data such as calendars and contacts. Tuta
• Supports custom domains on paid plans. Tuta
• Strong privacy focus and German/EU privacy framework. Tuta

Trade-off:

• It is more of a closed encrypted ecosystem; people who need traditional email-client workflows may find it less flexible. Proton

Domain and DNS setup

Regardless of provider, configure:

• SPF — prevents unauthorized servers from sending as your domain
• DKIM — cryptographically signs outgoing messages
• DMARC — tells receiving servers how to handle spoofed messages

These are especially important for a health blog because impersonation emails can damage trust. Proton provides setup guidance for these DNS protections when configuring a custom domain. Proton

Extra privacy recommendations for a health blog

• Do not ask readers to send medical records or detailed health histories by ordinary email.
• Put a disclaimer near your contact form: > “Please do not send private medical information through email. Messages are not a substitute for professional medical advice.”
• Use a separate newsletter provider or privacy-conscious mailing system rather than mixing subscriptions with your personal inbox.
• Enable: - hardware security keys (if supported)
• 2FA
• recovery codes stored offline
• domain registrar lock
• Consider a separate domain email for administration: - admin@yourdomain.com
• contact@yourdomain.com
• newsletter@yourdomain.com

My recommendation

For most health-focused blogs:

Domain registrar: privacy-respecting registrar + WHOIS privacy
Email: Proton Mail with custom domain
Security: hardware key + 2FA + SPF/DKIM/DMARC
Reader communications: encrypted contact workflow, with clear limits on sharing sensitive health information

If your blog will handle actual patient/client communications or regulated health data (for example HIPAA-covered information in the US), the requirements change significantly and you should choose a service and workflow designed for that compliance environment.

For a health-focused blog, I would prioritize:

1. Privacy of subscriber/member communications
2. Strong account security (2FA/passkeys)
3. Custom domain support (you@yourblog.com)
4. Reliable newsletters and contact forms
5. Clear separation between normal blog email and truly sensitive conversations

A good setup is usually hosted private email, not running your own mail server. Self-hosting sounds attractive, but maintaining spam reputation, patching, backups, DKIM/SPF/DMARC, and deliverability is a significant burden.

My top recommendation: Proton Mail + your custom domain

Proton Mail is the strongest fit if privacy is your main goal. It supports custom domains on paid plans and uses end-to-end encryption for Proton-to-Proton messages plus zero-access encryption for stored mail. Proton Proton

Suggested setup:

• Domain: yourhealthblog.com
• Email addresses: - hello@yourhealthblog.com — public contact
• newsletter@yourhealthblog.com — mailing list identity
• privacy@yourhealthblog.com — privacy inquiries
• you@yourhealthblog.com — personal/admin account
• Enable: - Hardware security key or passkey
• 2FA
• Recovery codes stored offline
• SPF, DKIM, and DMARC DNS records

Why it fits health content:

• Better privacy posture than advertising-funded email providers
• Useful if readers send personal health stories or sensitive questions
• Encryption is easier for nontechnical readers than traditional PGP workflows

Caution: Email itself is not automatically a HIPAA-compliant communication channel. If readers may send protected health information, you generally need a properly configured compliance solution and clear instructions not to submit sensitive medical information through ordinary email.

Alternative: Tuta Mail if you want maximum encryption defaults

Tuta Mail is another strong privacy choice. It encrypts mailboxes, calendars, and contacts by default and supports custom domains on paid plans. Tuta Tuta

Choose Tuta if you value:

• More aggressive encryption-by-default design
• Encrypted subject lines and metadata protection features
• Open-source clients

Trade-offs:

• Less compatibility with traditional email apps
• Fewer integrations than some competitors Proton

Best balance of usability: Fastmail

Fastmail is excellent if you need a normal business email experience: aliases, calendars, IMAP support, and smooth workflows. It encrypts data in transit and at rest, supports strong authentication, and does not rely on advertising. Fastmail

The trade-off:

• It is not a zero-access end-to-end encrypted mailbox provider in the same way Proton or Tuta are. Fastmail

Recommended architecture for a health blog

A privacy-conscious setup could look like:

Domain registrar

• Use a privacy-protective registrar with WHOIS privacy enabled.

Email hosting

• Proton Mail (primary recommendation)

Newsletter platform

• Keep marketing/newsletter sending separate from your private inbox.
• Use a provider designed for newsletters so unsubscribe handling and deliverability are handled correctly.

Website contact form

• Avoid sending form submissions directly to a personal inbox.
• Use: - spam protection
• encrypted storage if collecting sensitive information
• a disclaimer such as “Do not submit personal medical information through this form.”

Security checklist

• ✅ Enable 2FA/passkeys
• ✅ Use a password manager
• ✅ Enable DMARC (p=quarantine initially, later p=reject when confident)
• ✅ Use separate admin and public email addresses
• ✅ Keep backups of domain DNS settings
• ✅ Avoid collecting unnecessary health information

My pick

For a health-focused blog:

Best privacy: Proton Mail + custom domain
Most encryption-focused: Tuta Mail + custom domain
Best everyday email experience: Fastmail + custom domain

If your blog is run by a small team, I would lean toward Proton Mail Business; if it is a solo educational blog, a paid Proton Mail plan with a custom domain is usually enough. Proton

For a health-focused blog, I’d recommend Tuta Mail with your own domain rather than literally running an email server yourself.

Tuta offers a particularly strong privacy/security combination: its mailbox data is end-to-end encrypted, including message bodies, attachments, subject lines, calendars, and contacts, and its servers are operated in Germany. It also supports post-quantum cryptography. Tuta Tuta

Recommended setup

• Domain: yourblog.com from a reputable domain registrar.
• Email: Tuta Business using addresses such as hello@yourblog.com, editor@yourblog.com, and privacy@yourblog.com.
• Encryption: Tuta-to-Tuta messages are automatically end-to-end encrypted. For people using Gmail, Outlook, etc., Tuta can send password-protected encrypted messages, which is useful when handling potentially sensitive communications. Tuta
• Domain security: Configure SPF, DKIM, DMARC, and MTA-STS. Tuta supports all of these for custom domains. Tuta Tuta
• Account security: Require 2FA, use a unique long password, and keep recovery credentials offline.
• Website separation: Don't use the same mailbox for WordPress/admin authentication. Use separate admin credentials and, ideally, a dedicated security email.
• Minimize collected health information: Even with encrypted email, don't encourage readers to send medical records, diagnoses, or other unnecessary sensitive information unless you have a specific secure workflow and appropriate legal/compliance controls.

tuta.com

Why Tuta over Proton?

Proton Mail is my runner-up. Proton also supports custom domains and end-to-end encryption, and its Swiss jurisdiction is attractive from a privacy perspective. Proton

I'd pick Tuta if your priority is maximum built-in encryption and minimizing metadata exposure. Tuta encrypts subject lines and its contacts/calendar as well, doesn't provide traditional IMAP because of its encryption architecture, and its clients are open source. Tuta

I'd pick Proton if compatibility with conventional email applications is more important; Proton Mail Bridge supports clients such as Thunderbird, Apple Mail, and Outlook. Proton

One important distinction

If by "host email on my own domain" you mean "I want the domain to be mine", Tuta is an excellent fit.

If you mean "I want to operate the mail server myself on my own VPS", I wouldn't recommend that for a health blog unless you're comfortable administering Linux, spam reputation, backups, TLS, DKIM/DMARC, intrusion prevention, monitoring, and security updates. Self-hosting gives you more control, but it also makes you responsible for protecting the potentially sensitive contents.

Bottom line: yourdomain.com + Tuta Business + 2FA + SPF/DKIM/DMARC/MTA-STS is the setup I'd choose for a privacy-first health blog.

For a health-focused blog, I’d prioritize privacy without taking on unnecessary operational risk. My recommendation is Proton Mail with your own domain, rather than physically self-hosting the mail server.

Recommended setup: Proton Mail + your domain

Use something like:

you@yourhealthblog.com

with Proton handling the mail infrastructure.

Why I’d choose it:

• End-to-end encryption: Messages between Proton users are E2EE, while incoming mail from outside providers gets zero-access encryption. Proton Proton
• Custom domain support: Paid Proton plans support addresses on your own domain. Proton
• Encrypted external communication: You can send password-protected encrypted messages to people who don't use Proton. Proton
• Strong account security: Use 2FA, ideally with a hardware security key, and keep recovery credentials offline.
• Good domain authentication: Configure SPF, DKIM, and DMARC to prevent spoofing and improve deliverability. Proton
• Particularly sensible for health content: You avoid having to personally maintain a publicly exposed mail server, patch it, fight spam/abuse, maintain TLS certificates, and secure backups.

proton.me

If you specifically mean self-hosted

If by "on my own" you mean the server itself must be under your control, I'd look at Stalwart Mail Server first, with mailcow as the more feature-rich alternative.

Stalwart is particularly interesting for privacy because Privacy Guides notes that its PGP implementation supports encrypted message storage and, with WKD plus a compatible client such as Thunderbird, can provide self-hosted E2EE interoperability with Proton Mail users. Privacy Guides

Mailcow is easier to recommend if you want an integrated package with webmail, spam/antivirus tooling, DKIM, administration and 2FA. It supports TLS for IMAP/SMTP and automated Let's Encrypt certificates. Mailcow Documentation Mailcow Documentation

The catch is that self-hosting email doesn't automatically mean end-to-end encrypted email. TLS protects mail while it's traveling between servers, but ordinary SMTP ultimately involves other mail servers that may be able to access the message. For genuinely sensitive health-related correspondence, PGP/E2EE needs to be part of the workflow.

My architecture for your blog

I'd use:

Website: privacy-conscious hosting
→ Domain/DNS: reputable registrar + DNS provider
→ Email: Proton Mail custom domain
→ Sensitive correspondence: Proton-to-Proton or password-protected encrypted messages
→ Domain protection: SPF + DKIM + DMARC
→ Accounts: 2FA/security keys + unique passwords
→ Public contact form: collect the minimum information possible

One important distinction: a health blog isn't automatically a HIPAA environment. If readers might send you personal medical information, I'd explicitly discourage them from putting diagnoses, medical records, or other sensitive health information into an ordinary contact form or email unless you've designed the entire system for that purpose.

For your use case, I'd choose Proton over self-hosting unless you already have Linux/server administration experience and specifically want infrastructure ownership. It gives you most of the privacy benefits with substantially less chance that a misconfigured mail server becomes the weakest link. Proton Proton

For a health-focused blog, I’d prioritize privacy without taking on the operational risk of running your own mail server.

My recommendation: Proton Mail + your domain

Proton is probably the best fit if your priority is strong privacy/encryption with minimal maintenance.

You can use addresses such as hello@yourblog.com and contact@yourblog.com on your own domain. Proton supports custom domains on paid plans and provides end-to-end encryption between Proton users, plus zero-access encryption for stored mail. Proton Proton

proton.me

Recommended setup

• Domain: Keep your domain with a registrar you trust.
• Email: Proton Mail with the custom domain.
• Addresses: hello@, contact@, privacy@, perhaps editor@.
• Security: Enable 2FA, preferably with a hardware security key/passkey.
• DNS: Configure SPF, DKIM and DMARC. These protect against spoofing and improve deliverability. Proton
• Sensitive correspondence: Use Proton-to-Proton E2EE where possible. For recipients outside Proton, use Proton's password-protected/encrypted-mail options when appropriate.
• Desktop clients: Proton Mail Bridge allows compatible clients such as Thunderbird to access mail through IMAP/SMTP. Proton

One important caveat: ordinary email is not automatically end-to-end encrypted just because your mailbox is encrypted. E2EE depends on the recipient/service and how the message is sent. That's particularly important for a health-oriented publication: don't encourage readers to email you medical records, diagnoses, insurance information, etc. unless you've established an appropriate secure intake process.

If you literally want to self-host

I'd choose Stalwart or mailcow rather than building an email server from scratch.

Privacy Guides specifically recommends Stalwart for self-hosting and notes that its PGP implementation can provide encrypted message storage and, with WKD plus a compatible client, E2EE compatibility with Proton Mail. Privacy Guides

mailcow is another strong option: it packages mail delivery, webmail, spam/virus filtering, DKIM, administration and other components into a Docker-based system. Its documentation also describes encrypted mail storage and TLS-secured client connections. Privacy Guides Mailcow Documentation

The downside is substantial: you become the email administrator. You have to maintain the server, backups, TLS, DNS, spam reputation, security updates, monitoring and deliverability. mailcow currently recommends at least 6 GiB RAM plus swap for a minimal installation. Mailcow Documentation

What I'd choose

For your particular use case, I'd go with Proton + your domain, and keep the blog itself completely separate from the mail infrastructure. If you expect readers to submit health information, I'd also set up a dedicated encrypted contact/intake mechanism rather than simply publishing contact@domain.com.

proton.me

If you tell me whether you're technical enough to administer a Linux server and roughly how many mailboxes you need (1, 5, 20+), I can recommend a concrete setup and approximate cost.

For a health-focused blog, I’d recommend hosted private email rather than running your own mail server. Self-hosting gives you control, but email deliverability, spam reputation, backups, patching, and security become your responsibility.

My top pick: Tuta Mail

Tuta is probably the best fit if privacy and encryption are your highest priorities.

• Use your own domain, e.g. hello@yourhealthblog.com. Tuta Tuta
• Mail, attachments, subject lines, contacts, and calendars are encrypted end-to-end. Tuta Tuta
• Tuta says its servers are in Germany and that mailbox data is stored encrypted in ISO 27001-certified data centers. Tuta
• It supports password-protected encrypted messages to people who don't use Tuta. Tuta
• Its business plans support multiple users, aliases, custom domains, and catch-all addresses. Tuta
• Tuta also uses post-quantum cryptographic algorithms in its encryption architecture. Tuta

tuta.com

Strong alternative: Proton Mail

Proton would be my second choice, particularly if you want a more conventional business-email experience.

Proton supports custom domains, E2EE between Proton users, zero-access encryption for incoming external mail, 2FA, and SPF/DKIM/DMARC configuration. Proton Proton Proton Proton also specifically offers a healthcare-oriented solution and describes support for HIPAA-related use cases. Proton

proton.me

How I'd configure it

For a health blog, I'd set up:

• hello@domain.com — general inquiries
• editor@domain.com — editorial correspondence
• privacy@domain.com — privacy/data requests
• tips@domain.com — reader submissions, if applicable

Then configure SPF, DKIM, and DMARC for the domain. These help prevent someone else from spoofing your addresses. Proton

I'd also enable 2FA/security keys, use unique passwords, and keep the domain registrar account protected with 2FA.

One important health-privacy caveat

If readers might send you patient-identifiable health information, don't assume that "encrypted email" automatically makes the entire workflow legally compliant. Email encryption protects the transmission/storage architecture, but you also need appropriate policies, access controls, retention practices, and—if applicable—a provider agreement/BAA and regulatory compliance.

Bottom line: I'd choose Tuta + your own domain for a privacy-first independent health blog. Choose Proton instead if you value its broader business ecosystem and healthcare/compliance offerings more highly.

For a health-focused blog, I would prioritize privacy, domain reputation, deliverability, and the ability to protect sensitive communications (for example, reader questions that may contain health information). A good setup usually avoids running your own mail server unless you have strong server administration experience; self-hosted email is notoriously difficult to secure and keep out of spam filters.

Here are the strongest options:

Best overall: Proton Mail with your custom domain

Best for: a health blog where privacy is the top priority.

Why it fits:

• Supports custom domains on paid plans.
• Uses a zero-access encryption model for stored mail, meaning the provider is designed so it cannot simply read your mailbox contents. Expert Insights EmailAlias
• Strong privacy reputation and Swiss jurisdiction.
• Supports encrypted communication with other Proton users and OpenPGP-based encrypted email workflows for compatible recipients. PrivacyPilotHQ
• Good for addresses like: - hello@yourhealthblog.com
• privacy@yourhealthblog.com
• consultations@yourhealthblog.com

Trade-offs:

• Some advanced email workflows are less compatible than traditional IMAP-based providers.
• Email sent to ordinary Gmail/Outlook users will not automatically become end-to-end encrypted unless you use compatible encryption methods or secure-message workflows. EU Vetted

For a health blog, I would use:

• Proton Mail for the main inbox.
• A separate newsletter platform that supports privacy-conscious practices.
• A contact form that warns readers not to submit medical records or highly sensitive details by email.

Best if you want traditional email apps: Fastmail

Best for: a professional blog/business workflow where you want excellent email usability.

Advantages:

• Custom domain support.
• Excellent mail search, calendars, aliases, and standard email client support.
• Privacy-focused business model compared with advertising-supported providers. Gblock

Trade-off:

• It is not designed around provider-zero-access end-to-end encryption in the same way Proton Mail is. Gblock

Good choice if your priority is:

"I need reliable professional email and privacy improvements over mainstream providers."

Strong encryption alternative: Tuta

Best for: maximum encryption focus.

Advantages:

• End-to-end encryption is central to its design.
• Encrypts more mailbox components than many traditional providers.
• Privacy-oriented jurisdiction and architecture. Expert Insights EU Vetted

Trade-offs:

• Less compatible with traditional third-party email clients.
• Workflow changes may be needed.

A setup I would recommend for a health blog

Domain

Use a reputable domain registrar and enable:

• Domain privacy protection
• DNSSEC (if supported)
• Strong registrar account security

Email provider

My ranking:

1. Proton Mail — best privacy/security balance
2. Tuta — strongest encryption-first approach
3. Fastmail — best usability/privacy compromise

Security configuration

Enable:

• Hardware security key or passkey for your email account
• Two-factor authentication
• Recovery codes stored offline
• SPF
• DKIM
• DMARC (start with monitoring mode, then enforce)

Protect readers

Because this is health-related:

• Put a disclaimer on your contact page: - "Email is not a secure channel for sharing medical records or urgent health concerns."
• Avoid collecting unnecessary personal health information.
• Use a dedicated newsletter system rather than exposing your personal inbox.
• Consider a secure form solution if readers may submit sensitive questions.

If you expect to communicate with patients/clients, collect health questionnaires, or handle regulated health information, the recommendation changes because you may need a provider and workflow designed around compliance requirements rather than just private email. listicler.com

For a health-focused blog, I’d prioritize privacy, encrypted storage, strong account security, and reliable deliverability over simply “running your own mail server.”

My recommendation: Proton Mail + your own domain

Proton is probably the best fit if by “my own domain” you mean you@yourblog.com while still wanting strong privacy without becoming a mail-server administrator.

Proton supports custom domains on paid plans, and its mail system provides end-to-end encryption for Proton-to-Proton messages and zero-access encryption for stored mail. Proton Proton

proton.me

Recommended setup

• Domain: yourhealthblog.com
• Email: Proton Mail with addresses such as hello@yourhealthblog.com, contact@yourhealthblog.com, and privacy@yourhealthblog.com
• DNS security: SPF + DKIM + DMARC, ideally with DMARC enforcement once you've verified everything. Proton specifically recommends these for custom domains. Proton
• Account security: hardware security key/passkey or strong 2FA, unique password, recovery information stored securely.
• Sensitive reader communications: use Proton's encrypted-mail options rather than assuming ordinary email is confidential.
• Blog forms: don't automatically dump health-related form submissions into ordinary email. If readers might disclose diagnoses, medications, symptoms, etc., I'd use a dedicated secure form/contact system instead.

One important distinction: email encryption isn't automatically end-to-end encrypted just because you're using a privacy-focused provider. If you send from Proton to Gmail, for example, ordinary email encryption in transit does not mean the Gmail recipient's mailbox is inaccessible to Google. Proton supports password-protected encrypted messages for recipients outside Proton when appropriate. Proton

If you literally want to self-host the mail server

Then I'd look at Stalwart or mailcow, rather than building Postfix/Dovecot yourself.

privacyguides.org

Stalwart is particularly interesting for your use case because it supports encrypted message storage and PGP, including Web Key Directory (WKD), which can make encrypted communication with compatible clients much easier. Privacy Guides

docs.mailcow.email

Mailcow is the more conventional all-in-one self-hosted choice: it bundles mail services, webmail, spam/antivirus tooling, administration and 2FA, and supports TLS for IMAP/SMTP. Mailcow Documentation Its current documentation also supports automated Let's Encrypt certificates and DNS-01 challenges. Mailcow Documentation Mailcow Documentation

The trade-off

For a solo health blogger, I'd choose Proton. You retain your own domain and get substantially less operational risk than maintaining an internet-facing mail server yourself.

If your blog will collect health information from readers or patients, that's a different level of requirement: I'd design the contact/submission system separately from the blog's ordinary email and consider the applicable HIPAA/privacy obligations rather than treating encrypted email alone as sufficient.

For a health-focused blog, I’d use a privacy-focused hosted email provider rather than running your own mail server. Self-hosting gives you control, but email deliverability, spam reputation, backups, patching, and encryption become your responsibility.

My recommendation: Tuta Mail + your domain

Tuta is my top pick if privacy and encryption are the priorities.

• Custom domain: Use addresses such as hello@yourhealthblog.com; paid plans support custom domains and unlimited addresses/aliases on your own domain. Tuta Tuta
• End-to-end encryption: Tuta encrypts email contents, attachments, subject lines, contacts, and calendars. Tuta
• Post-quantum cryptography: Tuta currently uses X25519 and Kyber-1024 in its encryption architecture. Tuta
• German hosting: Tuta says business data is stored on its own servers in Germany, with GDPR protections. Tuta
• External recipients: You can send password-protected encrypted messages to people who don't use Tuta. That's particularly useful if you're communicating with contributors or readers about sensitive topics. Tuta
• Domain security: Tuta supports SPF, DKIM and DMARC, which are important for preventing spoofing and protecting your domain's reputation. Tuta
• Open-source clients: Tuta's desktop clients are open source, and it deliberately doesn't use conventional IMAP because doing so would require exposing decrypted mail to an IMAP client. Tuta

tuta.com

Proton Mail is the strongest alternative

Proton would be my second choice. It supports custom domains, end-to-end encryption, open-source software and Swiss privacy protections. Proton also specifically advertises support for business communications involving GDPR, HIPAA and CCPA requirements. Proton

proton.me

I'd choose Proton if you value broader interoperability—Proton Mail Bridge can work with applications such as Thunderbird, Apple Mail and Outlook. Proton

Important health-blog caveat

If your blog will handle actual patient/client health information, don't assume that choosing an encrypted email provider automatically makes you HIPAA-compliant. You'd need to consider the entire workflow—your website forms, analytics, hosting, backups, email recipients, access controls, and applicable agreements/compliance requirements.

For a normal health-information blog—newsletter correspondence, reader questions, author communications, etc.—Tuta + a custom domain + strong DNS security is an excellent privacy-oriented setup.

Suggested setup

yourhealthblog.com
→ domain registrar with 2FA
→ Tuta Mail for email hosting
→ SPF + DKIM + DMARC + MTA-STS
→ separate aliases such as hello@, contact@, press@
→ hardware/security-key or strong 2FA on the administrator account
→ avoid collecting sensitive health information through ordinary web contact forms

One subtle point: email encryption doesn't mean every email you send is automatically end-to-end encrypted with everyone. Encryption is strongest when both sides use compatible encrypted mail, or when you deliberately use a password-protected encrypted message for an external recipient. Tuta supports the latter. Tuta

If you tell me whether you're a solo blogger or a small team, I can give you a concrete domain + email architecture (including DNS records and a privacy-preserving contact form) without making it unnecessarily complicated.

For a health-focused blog, I’d recommend using your own domain with Proton Mail rather than running the mail server yourself.

Best overall: Proton Mail + your domain

Proton is a particularly good fit if privacy is more important than having physical control of the mail server.

• Custom domain: You can use addresses such as contact@yourblog.com; custom domains require a paid Proton plan. Proton Proton
• Encryption at rest: Proton uses zero-access encryption, meaning Proton says it cannot decrypt the stored contents of your mailbox. Proton Proton
• End-to-end encryption: Mail between Proton users is automatically E2EE. For people using Gmail, Outlook, etc., you can send password-protected encrypted messages or use OpenPGP. Proton Proton
• Strong domain authentication: Configure SPF, DKIM and DMARC to prevent spoofing and improve deliverability. Proton Proton
• Good separation from your blog: Keep your website hosting and email provider separate, so compromising the WordPress/blog server doesn't automatically compromise the mailbox.
• Particularly appropriate for health content: If readers might contact you about sensitive personal matters, minimizing provider access to mailbox contents is valuable. However, don't treat ordinary email as automatically HIPAA-compliant just because it's encrypted; if you're actually handling protected health information as a covered entity/business associate, you'll need to evaluate the applicable legal and contractual requirements separately.

proton.me

If you literally want to self-host

I'd look at Stalwart Mail Server first, with Mailcow as another mature option. Privacy Guides specifically highlights Stalwart's encrypted message storage and OpenPGP/WKD capabilities, while Mailcow provides a more complete Docker-based mail stack with webmail, DKIM, spam/antivirus controls and 2FA. Privacy Guides

The trade-off is substantial: you become responsible for backups, patching, spam reputation, TLS, DNS, intrusion protection, monitoring, deliverability and recovery. For a blog, that's usually not worth the operational burden unless "the provider must never possess the mailbox keys" is a hard requirement.

My recommended architecture

Domain registrar → DNS with DNSSEC → Proton Mail → contact@yourdomain.com

Then:

• Use a separate address such as newsletter@... for mailing-list software.
• Use contact@... for reader correspondence.
• Enable 2FA/passkeys on the Proton account.
• Use a long, unique account password and store recovery information securely.
• Configure SPF + DKIM + DMARC, ideally moving DMARC toward enforcement once you've verified legitimate senders.
• Don't collect medical histories or other sensitive information through a public contact form unless you have a specific reason and appropriate safeguards.
• If you need genuinely confidential conversations with readers, provide an encrypted-contact option (PGP or Proton Mail) rather than implying that ordinary email is end-to-end encrypted.

Bottom line: For your use case, I'd choose Proton Mail with your own domain. It gives you substantially better privacy and encryption than conventional hosted email without turning you into your own mail administrator. If you tell me whether this is a personal blog, nonprofit, or business, I can also recommend the appropriate Proton plan and a privacy-focused DNS/domain setup.

The trade-off is substantial: you become responsible for backups, patching, spam reputation, TLS, DNS, intrusion protection, monitoring, deliverability and recovery. For a blog, that's usually not worth the operational burden unless "the provider must never possess the mailbox keys" is a hard requirement.

My recommended architecture

Domain registrar → DNS with DNSSEC → Proton Mail → contact@yourdomain.com

Then:

For a health-focused blog, I’d prioritize privacy, encryption, deliverability, and low operational burden over literal server ownership.

My recommendation: Proton Mail + your own domain

Use Proton Mail with an address such as hello@yourhealthblog.com.

Proton supports custom domains on paid plans, and its mail system provides end-to-end encryption between Proton users plus zero-access encryption for externally received mail. It also supports password-protected encrypted messages for recipients who aren't on Proton. Proton Proton Proton

proton.me

Why I’d choose it for a health blog

• Strong privacy: Proton says it cannot access the contents protected by its zero-access encryption architecture. Proton
• Custom domain: You can use contact@yourdomain.com, editor@yourdomain.com, etc., rather than a Proton address. Proton
• Encryption: Proton-to-Proton mail is automatically E2EE; external recipients can receive password-protected encrypted messages. Proton Proton
• Domain authentication: Proton supports SPF, DKIM, and DMARC, which are important for preventing spoofing and keeping legitimate newsletters out of spam folders. Proton
• 2FA/security controls: Business accounts support enforced 2FA and hardware security keys such as YubiKeys. Proton
• Less maintenance: You aren't responsible for keeping an Internet-facing mail server patched, monitored, backed up, and out of spam blacklists.

proton.me

If you literally want to self-host

I'd look at mailcow or Stalwart Mail Server.

Mailcow is a particularly complete option: it bundles mail services, DKIM, spam/antivirus protection, webmail, administration, and 2FA. Its documentation also supports TLS/SSL and the usual SPF/DKIM/DMARC setup. Mailcow Documentation Mailcow Documentation Mailcow Documentation

docs.mailcow.email

For maximum privacy, Stalwart is especially interesting because Privacy Guides notes its PGP implementation can provide encrypted message storage and, with WKD plus a compatible client such as Thunderbird, self-hosted E2EE interoperability with Proton Mail users. Privacy Guides

The catch is that self-hosting email is a security/operations project, not simply installing software. You'd need reliable backups, server hardening, TLS, DNS authentication, monitoring, spam protection, reputation management, and ongoing patching.

One important health/privacy distinction

If your blog allows readers to send personal health information, don't assume that "encrypted email" automatically makes the entire setup legally compliant. Ordinary email to Gmail/Yahoo/etc. isn't end-to-end encrypted merely because your server uses TLS. I'd design the contact workflow so readers don't submit medical records or sensitive health information by ordinary email—for example, explicitly instruct them not to include such information.

Bottom line: For a one-person or small health blog, I'd choose Proton Mail + your domain + SPF/DKIM/DMARC + hardware-key 2FA. If "I must physically control the mail server" is a hard requirement, I'd choose Stalwart or mailcow on a hardened VPS, with client-side PGP/E2EE for genuinely sensitive correspondence.

For a health-focused blog, I’d recommend self-hosted mailcow on a reputable VPS if “I control the server and data” is the priority. If you mainly want strong privacy with minimal maintenance, Proton Mail with your custom domain is the better overall choice.

My recommendation: mailcow + encrypted VPS

docs.mailcow.email

Mailcow is a full, open-source mail stack built around Postfix/Dovecot, with SOGo webmail, DKIM, spam filtering, 2FA/WebAuthn, TLS controls, and administration through a web interface. Privacy Guides currently recommends mailcow among self-hosted options and specifically notes its 2FA and webmail capabilities. Privacy Guides Mailcow Documentation

For your use case, I'd configure it roughly like this:

• Domain: yourblog.com
• Mail server: mail.yourblog.com
• Hosting: a VPS from a provider you trust, preferably in a jurisdiction appropriate to your privacy requirements.
• TLS: Require TLS for client connections; mailcow supports IMAPS/SMTPS and STARTTLS. Mailcow Documentation
• MTA-STS: Enable it in enforce mode after testing. Mailcow supports MTA-STS directly in current versions. Mailcow Documentation
• Authentication: Use strong unique passwords plus TOTP/WebAuthn/2FA. Mailcow supports TFA including WebAuthn and TOTP. Mailcow Documentation
• Email authentication: Configure SPF + DKIM + DMARC, ideally with DMARC enforcement once you're confident legitimate mail passes. Mailcow provides tools for these. Mailcow Documentation
• Storage: Use encrypted VPS disks/volumes where available, and encrypt your backups separately.
• Backups: Keep encrypted, off-server backups. Mailcow specifically recommends regular backups and supports encrypted Borgmatic backups. Mailcow Documentation
• Admin account: Separate administrator identity from your public contact@ address, with 2FA and no unnecessary admin access.

An important caveat about "encrypted email"

Self-hosting does not automatically give you end-to-end encrypted email.

TLS can protect mail while it's being transmitted between compatible servers, and mailcow can encrypt its stored mail data. Mailcow Documentation But ordinary email sent to Gmail, Outlook, etc. generally isn't end-to-end encrypted.

For genuinely sensitive health-related correspondence, I'd add OpenPGP for messages where both parties can use it. An interesting alternative is Stalwart, which Privacy Guides highlights because its PGP implementation can provide encrypted message storage and can work with Web Key Directory for easier OpenPGP interoperability. Privacy Guides

Easier alternative: Proton Mail + your domain

proton.me

If you're running a blog rather than an IT operation, I'd actually choose Proton Mail unless self-hosting itself is important to you.

You can use addresses such as hello@yourblog.com with your own domain on a paid Proton plan. Proton Proton also provides end-to-end encryption between Proton users and zero-access encryption for externally received mail. Proton

The tradeoff is straightforward:

*Assuming the VPS provider itself isn't trusted with the server's plaintext data; full protection against a provider with privileged access requires additional measures.

Bottom line: For a health-focused blog, I'd pick Proton + your domain unless you specifically want to operate your own mail infrastructure. If maximum control is the goal, mailcow + encrypted VPS + encrypted backups + OpenPGP for sensitive messages is the setup I'd build.

For a health-focused blog, I’d prioritize a provider that gives you:

• Custom domain support (you@yourblog.com)
• Strong encryption at rest and ideally end-to-end encryption (E2EE)
• No advertising-based business model
• Good spam protection
• Aliases (for newsletters, contact forms, partnerships)
• Reliable deliverability (important for readers and healthcare organizations)
• Compliance awareness if you ever receive sensitive reader messages

A key caveat: email is not automatically HIPAA-compliant just because it is encrypted. If readers send personal health information (PHI), you may need a provider and workflow specifically designed for HIPAA requirements, including a Business Associate Agreement (BAA). Avoid encouraging readers to send medical details through ordinary contact email.

My top recommendation: Proton Mail with your own domain

proton.me is probably the best balance for a privacy-oriented health blog.

Why it fits:

• Supports custom domains on paid plans. Proton
• Uses end-to-end encryption for Proton-to-Proton messages and zero-access encryption for stored mailbox data. Proton
• Based in Switzerland, which many privacy-conscious users consider a favorable jurisdiction. Proton
• Good ecosystem if you later want private storage, password management, or calendars. Proton
• Supports aliases, useful for separating: - hello@domain.com
• press@domain.com
• newsletter@domain.com
• partnerships@domain.com

A practical setup:

• Domain registrar: keep your domain with a separate registrar
• DNS: - SPF enabled
• DKIM enabled
• DMARC enabled
• Mail: - Proton Mail custom domain
• Contact forms: - Route submissions to a dedicated mailbox
• Add a warning: “Please do not send personal medical information”

Strong alternative: Tuta Mail

tuta.com is worth considering if maximum privacy is the priority.

Advantages:

• End-to-end encryption approach
• Encrypts more mailbox metadata than many traditional systems, including subject lines. Privacy Ranker
• German/EU privacy environment. Tuta
• Supports custom domains on paid plans. Privacy Ranker

Trade-offs:

• Less compatible with traditional email clients.
• Better if you are happy using their apps/web interface. Privacy Ranker

Best usability choice: Fastmail

fastmail.com is excellent if you care more about workflow than maximum encryption.

Strengths:

• Excellent custom domain support
• Very good spam filtering
• Works well with normal email clients
• Subscription-based (not advertising-supported)

Trade-off:

• It does not provide the same end-to-end encryption model as Proton or Tuta; the provider can technically access mailbox contents. Privacy Decoded

What I would choose for your situation

For a health blog:

1. Privacy-first independent blogger: Proton Mail + custom domain
2. Highest privacy / minimal metadata exposure: Tuta Mail
3. Large audience + lots of email workflow needs: Fastmail

I would avoid self-hosting your own mail server unless you already manage Linux servers and email security. Running your own mail introduces risks around spam reputation, patching, backups, encryption configuration, and deliverability.

A solid health-blog email architecture would be:

• hello@yourdomain.com → public contact
• newsletter@yourdomain.com → mailing list platform
• admin@yourdomain.com → private account
• privacy@yourdomain.com → privacy requests
• Separate newsletter provider → avoid mixing subscriber databases with personal inboxes

If the blog will collect health questionnaires, patient stories, or any identifiable medical information, the recommendation changes because you’ll need to consider HIPAA-oriented email services and processes rather than just privacy-focused email.

For a health-focused blog, I’d prioritize privacy, account security, domain reputation, and the ability to handle sensitive reader communications. You probably don’t need to self-host a mail server (which is difficult to secure and maintain); a privacy-focused hosted service with your own domain is usually the stronger choice.

Recommended solution: Proton Mail with your custom domain

proton.me is my top recommendation for a health blog because it combines:

• Custom domain email (for example, hello@yourhealthblog.com) on paid plans. Proton
• Zero-access encryption for stored mail, meaning Proton cannot read your encrypted mailbox contents. Proton
• End-to-end encryption when communicating with other Proton users, plus support for encrypted messages to outside users via compatible methods. Proton Proton
• Strong account protections such as 2FA and a privacy-focused ecosystem (mail, calendar, storage, password manager). Proton

A practical setup:

• Domain registrar: keep your domain with a privacy-respecting registrar.
• Email provider: Proton Mail.
• Addresses: - hello@domain.com — public contact
• newsletter@domain.com — mailing list
• support@domain.com — reader questions
• you@domain.com — private admin account
• Enable: - 2FA with a hardware security key if possible
• SPF, DKIM, and DMARC DNS records
• Separate admin and public-facing email addresses

Strong alternative: Tuta Mail

tuta.com is worth considering if you want maximum encryption coverage.

Advantages:

• End-to-end encrypts stored mail, calendars, and contacts. Tuta Tuta
• Supports custom domains on paid plans. Tuta
• Strong privacy-by-design approach and German/EU data protection environment. Tuta

Tradeoffs:

• Less compatible with traditional email apps and workflows than some competitors. Proton

If you need a more traditional email experience

fastmail.com is excellent for usability:

• Very good custom-domain email hosting
• Strong spam filtering and reliability
• Good support for standard email clients

However, it is not an end-to-end encrypted mailbox provider, so it is less suitable if you expect readers to send private health-related information by email. Privacy Decoded

Important health-blog considerations

Email encryption does not automatically make you HIPAA compliant or suitable for handling protected health information (PHI). If your blog collects health questions, diagnoses, patient details, or consultations, you may need a dedicated secure intake system rather than ordinary email.

For a typical educational health blog, I’d use:

1. Proton Mail + custom domain for general communication.
2. A separate encrypted contact form service if readers may submit sensitive stories.
3. A disclaimer encouraging readers not to send medical records or private health details by email.
4. A newsletter platform chosen for privacy and compliance needs.

My default choice would be:

Best overall: Proton Mail + your domain
Most encryption-focused: Tuta Mail + your domain
Best everyday email workflow: Fastmail + your domain

For a solo health blogger, Proton Mail is likely the best balance of privacy, professionalism, and ease of use.

For a health-focused blog, I’d recommend self-hosting with Mailcow on a dedicated VPS, with Stalwart as the more privacy/security-oriented alternative.

My recommendation: Mailcow + encrypted backups

docs.mailcow.email

Mailcow gives you a mature, relatively manageable self-hosted mail stack with Postfix/Dovecot, webmail, spam filtering, DKIM, 2FA, and TLS. Its current documentation also supports MTA-STS, which helps require TLS for mail transport where supported. Mailcow Documentation Mailcow Documentation

For your domain, I'd configure:

• Dedicated VPS with a reputable provider and a static IPv4 address.
• Mailcow in Docker.
• TLS everywhere — HTTPS for webmail and encrypted IMAPS/SMTP connections. Mailcow supports Let's Encrypt certificates out of the box. Mailcow Documentation Mailcow Documentation
• SPF + DKIM + DMARC, preferably moving DMARC toward p=reject once you've verified legitimate sending. Mailcow provides configuration for all three. Mailcow Documentation
• MTA-STS in enforce mode after testing, to improve protection against downgrade/MITM attacks. Mailcow Documentation
• WebAuthn/TOTP 2FA for administrative and mailbox access. Mailcow Documentation
• Encrypted, off-server backups. Mailcow specifically recommends regular backups and supports encrypted Borgmatic backups. Mailcow Documentation
• Keep the blog and mail server separate. A compromise of WordPress/the blog shouldn't automatically expose your mail infrastructure.

One important distinction about "encryption"

Self-hosting doesn't automatically give you end-to-end encrypted email.

TLS protects mail while it travels between compatible mail servers and protects connections from your devices. But ordinary email is still potentially readable by the mail servers involved.

If you want stronger protection for sensitive health-related correspondence, I'd add OpenPGP for messages that actually need end-to-end encryption.

An especially interesting alternative is Stalwart. Privacy Guides currently recommends it among self-hosted mail servers and notes that its PGP implementation can provide encrypted message storage and, with WKD plus a compatible client such as Thunderbird, E2EE interoperability with Proton Mail users. Privacy Guides

If you don't actually need to run the server yourself

I'd seriously consider Proton Mail with your custom domain instead.

proton.me

It's considerably easier to operate and gives you zero-access encryption for stored mail and automatic E2EE between Proton users, while supporting custom domains on paid plans. Proton Proton

My choice for your use case:

For a health blog, I'd lean Proton if the mailbox is primarily for readers/contact, and Mailcow or Stalwart if owning the entire infrastructure is itself a requirement. Also, avoid asking readers to send medical records or highly sensitive health information through ordinary email; email encryption doesn't make an ordinary public contact address appropriate for handling clinical data.

For a health-focused blog, I’d recommend self-hosting mailcow on a dedicated VPS, with a few privacy/security layers around it.

Recommended setup

Domain: yourblog.com
Mail server: mailcow on a dedicated Linux VPS
Webmail: SOGo, included with mailcow
Encryption: TLS 1.2/1.3 for client connections + MTA-STS/DANE where practical
Authentication: DKIM + SPF + DMARC
Admin security: WebAuthn/FIDO2 or TOTP 2FA
Backups: encrypted, off-server backups

Mailcow is a particularly good fit because it gives you a fairly complete mail stack rather than requiring you to assemble Postfix, Dovecot, spam filtering, webmail, DKIM, etc. yourself. Its current stack includes Postfix, Dovecot, Rspamd, SOGo, DKIM handling, and TLS-security components. Mailcow Documentation Mailcow Documentation

Why I'd choose it

• You control the mailbox data. Unlike a hosted provider, you control the server, storage, logs, and backups.
• Strong transport encryption: mailcow supports encrypted IMAP/SMTP connections and currently supports MTA-STS; it also incorporates DANE/TLSA capabilities. Mailcow Documentation Mailcow Documentation
• Good domain authentication: mailcow's documentation recommends SPF, DKIM and DMARC, including a p=reject DMARC configuration once you're confident everything is working. Mailcow Documentation
• Strong administrator authentication: WebAuthn, YubiKey-based authentication and TOTP are supported. Mailcow Documentation
• Encrypted backups: mailcow specifically recommends regular backups and supports encrypted backup approaches such as Borgmatic. Mailcow Documentation

One important caveat about "encrypted email"

Self-hosting doesn't automatically mean end-to-end encrypted email.

TLS protects messages while they're traveling between your server and another mail server that supports TLS. It does not guarantee that the recipient's provider can't read the message after delivery.

For genuinely sensitive health-related correspondence, I'd therefore use a separate E2EE mechanism—for example, send a notification email saying "You have a secure message" and put the sensitive content behind an authenticated HTTPS page, rather than putting health information directly into ordinary email.

If you don't actually need to administer your own mail infrastructure, Proton Mail with your custom domain is the alternative I'd seriously consider. Proton supports custom domains on paid plans and provides E2EE between Proton users plus zero-access encryption for externally received mail. Proton Proton

My choice for your blog

One additional consideration: if the blog will collect information about people's medical conditions, symptoms, treatments, or other health information, treat that as a substantially higher-risk privacy project than ordinary blogging. Email infrastructure alone isn't enough—you'd want to minimize what you collect, restrict access, encrypt backups, keep logs to a minimum, and establish appropriate retention/deletion policies.

If you want true self-hosting, my concrete starting architecture would be mailcow + a hardened VPS + encrypted backups + Cloudflare/DNS only where appropriate + SPF/DKIM/DMARC + MTA-STS + WebAuthn 2FA.

For a health-focused blog, I would prioritize privacy, account security, domain reputation, and a good workflow for handling reader questions. You probably do not need to self-host an email server (it is difficult to secure, maintain deliverability, and prevent leaks). A privacy-focused hosted provider is usually the stronger option.

My top recommendations:

1. Best overall: Proton Mail with your custom domain

Best fit if you want: strong privacy + professional appearance + manageable setup.

Example:

• hello@yourhealthblog.com
• newsletter@yourhealthblog.com
• privacy@yourhealthblog.com

Advantages:

• End-to-end encryption between Proton users.
• Zero-access encryption for stored mail (the provider cannot simply read your mailbox contents).
• Supports custom domains on paid plans.
• Strong security features such as 2FA and domain authentication tools. proton.meproton.me

Trade-offs:

• Regular email sent to Gmail/Outlook users cannot magically become end-to-end encrypted unless the recipient uses compatible encryption or you use a protected-message workflow.
• Some integrations may be less convenient than traditional business email.

For a health blog, I would use:

• Proton Mail for your main identity and reader correspondence.
• A separate newsletter platform if you collect large subscriber lists.
• A dedicated address like contact@ rather than exposing your personal inbox.

2. Most privacy-maximal: Tuta Mail

Best fit if you want: maximum encryption coverage and minimal data exposure.

Advantages:

• End-to-end encryption is built into the service.
• Encrypts more mailbox data than many traditional providers, including subject lines and contacts. tuta.com
• Supports custom domains on paid plans. tuta.com
• Strong privacy orientation and German jurisdiction. tuta.com

Trade-offs:

• Less compatible with some third-party email clients and workflows compared with conventional email providers.
• If your blog grows into a business with many integrations, you may find Proton or a business-oriented provider easier.

3. Best usability compromise: Fastmail

Best fit if you want: a polished email experience with good privacy practices.

Advantages:

• Excellent email usability.
• Custom domains.
• Strong security features and no advertising business model. www.fastmail.com
• Works well with normal email apps.

Trade-off:

• It does not provide the same zero-access/end-to-end encrypted mailbox architecture as Proton or Tuta. www.fastmail.com

My suggested setup for a health blog

Domain

• Register your domain with a privacy-respecting registrar.
• Enable domain privacy where available.

Email

• Use Proton Mail or Tuta.
• Create separate addresses:
  • hello@domain.com — public contact
  • editor@domain.com — blog operations
  • privacy@domain.com — privacy requests
  • alerts@domain.com — account/security notifications

Security

• Use a hardware security key if possible (for example, a FIDO2/YubiKey-style device).
• Enable 2FA.
• Use a password manager.
• Configure:
  • SPF
  • DKIM
  • DMARC

These help prevent spoofing and improve deliverability. proton.meproton.me

Health-specific caution
If readers may send personal health information, avoid positioning ordinary email as a secure medical communication channel. Email encryption protects many risks, but it does not automatically make a setup compliant with healthcare regulations (such as HIPAA in the U.S.). If you will receive identifiable patient information, consider a dedicated secure intake system rather than ordinary inbox email.

My pick:

• Solo health blogger → Proton Mail + custom domain
• Privacy-first activist/research style blog → Tuta Mail
• Business blog needing lots of integrations → Fastmail or Proton Mail Business

For most health-focused blogs, Proton Mail is the best balance of privacy, professionalism, and ease of use.

For a health-focused blog, I would prioritize:

1. Strong privacy (especially because readers may contact you about sensitive health topics)
2. Custom domain support (e.g., hello@yourhealthblog.com)
3. Good spam/phishing protection
4. Encryption options
5. Reliable delivery (newsletters, reader inquiries, partnerships)

A good shortlist:

Privacy Decoded Proton## My recommendation for a health blog

Best balance: proton.me + your own domain

Example setup:

• you@yourblog.com → public contact address
• privacy@yourblog.com → privacy/legal inquiries
• newsletter@yourblog.com → mailing list identity
• Separate aliases for services and accounts

Why it fits:

• Readers may share personal health experiences, so minimizing provider access to mailbox contents is valuable.
• You can use your own domain rather than a provider address.
• You can add other privacy tools from the same ecosystem if needed. Proton

If you expect very sensitive reader messages

Consider:

tuta.com

Good if your priority is minimizing metadata exposure and maximizing encryption coverage. It encrypts more mailbox elements than many traditional providers, including subject lines within its system. Privacy Ranker Tuta

A possible approach:

• Public blog contact: contact@yourdomain.com
• Sensitive reader contact: secure@yourdomain.com on Tuta
• Tell readers not to send medical records or identifiable health information unless you have a proper process for handling it.

If your main goal is professional publishing

Choose:

fastmail.com

It is excellent for:

• editorial workflows
• assistants
• calendars
• normal email apps
• reliable sending

But it is a privacy-focused hosted email service rather than a zero-access encrypted mailbox. Privacy Decoded

Important health-blog privacy additions

Email alone does not make a health site private. I would also add:

• DMARC, DKIM, and SPF records for your domain to reduce spoofing.
• A separate newsletter provider that supports consent management and privacy compliance.
• Avoid collecting unnecessary health details through contact forms.
• Use encrypted forms if readers submit sensitive information.
• Enable hardware security keys or strong 2FA on your email account.
• Keep domain registration privacy enabled where available.

For most independent health writers, my ranking would be:

1. Proton Mail + custom domain — best overall choice
2. Tuta + custom domain — strongest privacy-first choice
3. Fastmail + custom domain — best usability choice

One caveat: ordinary email to Gmail/Outlook recipients is not magically end-to-end encrypted just because you use a private provider; the strongest protection applies when both sides support compatible encryption or when you use secure message options. Privacy Ranker

For a health-focused blog, I’d recommend Tuta Mail with your own domain rather than literally running the mail server yourself.

My pick: Tuta Mail + your domain

Tuta Mail is particularly well suited if privacy is the priority:

• End-to-end encryption by default for email, attachments, calendars, and contacts; Tuta says mailbox data is encrypted so that it isn't accessible to Tuta itself. tuta.com
• Custom-domain support, so you can use addresses such as hello@yourblog.com rather than a provider-branded address. tuta.com
• Password-protected encrypted messages to non-Tuta recipients, useful if readers, contributors, or sources need to send you sensitive material. tuta.com
• Servers are operated in Germany, with GDPR protections and ISO 27001-certified data centers. tuta.com
• Tuta supports SPF, DKIM, DMARC and MTA-STS for a custom domain, which are important for preventing spoofing and improving mail security. tuta.com
• Its clients are open source, and it supports 2FA. tuta.com

For a blog, I'd create separate addresses such as:

hello@yourdomain.com — general correspondence
editor@yourdomain.com — contributors
privacy@yourdomain.com — privacy/data inquiries
newsletter@yourdomain.com — automated blog mail

One important caveat

Email encryption has a fundamental limitation: you don't control the recipient's email system. Tuta-to-Tuta mail can be end-to-end encrypted, while messages to ordinary Gmail/Outlook/etc. accounts aren't automatically E2EE in the same way. For sensitive communications with outsiders, use Tuta's password-protected encrypted-mail mechanism rather than assuming ordinary email is confidential. tuta.com

Alternatives

Proton Mail is my second choice. Proton Mail supports custom domains on paid plans and provides E2EE between Proton users plus zero-access encryption for externally received mail. proton.me It's an excellent choice if you want a more conventional email ecosystem.

Migadu is interesting if you specifically want standard IMAP/SMTP/POP3 and lots of addresses/domains. Migadu It says traffic is encrypted and that it doesn't advertise or track users, but it doesn't offer the same provider-side end-to-end encryption model as Tuta. migadu.com

What I'd deploy

Domain registrar/DNS → Tuta Mail → your blog

Then configure:

1. A privacy-conscious domain registrar.
2. Tuta as your MX provider.
3. SPF + DKIM + DMARC (I'd use a strict DMARC policy once you've verified everything works).
4. MTA-STS/TLS where supported.
5. 2FA with a hardware security key or authenticator.
6. Unique passwords and secure recovery credentials.
7. Separate addresses/aliases for public-facing functions.
8. Keep reader health information out of ordinary email whenever possible. If your blog solicits personal health information, email encryption alone doesn't automatically make your setup HIPAA-compliant or otherwise appropriate for regulated health data.

If by "host email on my own domain" you specifically mean run the mail server yourself on a VPS, rather than using a privacy-focused hosted provider, I'd choose a different architecture—e.g. Mailcow/Postfix + Dovecot + encrypted storage + hardened DNS/TLS. That gives you more control but substantially increases the security and maintenance burden.

For a health-focused blog, I’d avoid running your own mail server unless you have a strong operations/security background. Self-hosted email is difficult to secure, maintain, and keep out of spam folders. A privacy-focused hosted provider with your own domain usually gives a better security/privacy balance.

My top recommendation:

Best overall: Proton Mail with your custom domain

Proton Mail is a strong fit if your blog may involve readers sharing sensitive health experiences.

Why it fits:

• Custom domain support (for example, hello@yourhealthblog.com) on paid plans. proton.me
• Zero-access encryption architecture: Proton stores mail encrypted so it cannot normally read your mailbox contents. proton.me
• End-to-end encryption for Proton-to-Proton messages. proton.me
• Strong account security options, including hardware security keys and 2FA.
• Swiss jurisdiction and a privacy-focused business model.

Good setup for a health blog:

• hello@domain.com — public contact
• editor@domain.com — publishing/admin
• privacy@domain.com — privacy requests
• Separate private mailbox for your personal identity

Most privacy-maximal alternative: Tuta

Tuta Mail is worth considering if your priority is minimizing metadata exposure.

Strengths:

• End-to-end encryption is built into the service. tuta.com
• Encrypts more mailbox data than traditional email systems, including subject lines and attachments. tuta.com
• Supports custom domains on paid plans. tuta.com
• Privacy-first design with no advertising model. tuta.com

Tradeoff:

• It is less compatible with traditional email clients because it does not use normal IMAP access. tuta.com

Best if you want a normal email experience: Fastmail

Fastmail is excellent for professional blogging workflows:

• Very polished email/calendar experience.
• Custom domains supported. www.fastmail.help
• Good privacy practices and no advertising model.

Tradeoff:

• It is not designed around provider-proof end-to-end encryption in the way Proton and Tuta are. www.fastmail.helpprivacy-decoded.com

Security configuration I’d use for a health blog

Regardless of provider:

1. Use a domain registrar with privacy protection
   • Hide your personal registration details where allowed.

2. Enable:
   • Hardware security key (best)
   • 2FA
   • Strong unique password stored in a password manager

3. Configure email authentication:
   • SPF
   • DKIM
   • DMARC

These reduce spoofing and improve deliverability. Proton specifically recommends configuring these with custom domains. proton.me

4. Separate public contact from sensitive communication
   • A public blog inbox will receive spam.
   • Avoid mixing reader submissions with your personal mailbox.

5. Be careful with health information
   • Regular email is not automatically a HIPAA-compliant communication channel.
   • If readers may submit identifiable medical information, consider a dedicated secure intake form or a healthcare-compliant communication platform rather than ordinary email.

My pick:

• Most health/privacy-oriented: Proton Mail + custom domain
• Maximum privacy philosophy: Tuta + custom domain
• Most like traditional business email: Fastmail + custom domain

For a solo health blogger, I would choose Proton Mail with a custom domain plus a secure contact form that discourages sharing personal medical details.

For a health-focused blog, I’d prioritize privacy, control of stored mail, and strong encryption without making email administration a full-time job.

My recommendation: self-hosted Stalwart

Stalwart Mail Server is probably the best fit if “host it myself” is literal.

Why:

• You control the server and mailbox data, rather than handing your email archive to a hosted provider.
• It supports encrypted message storage and PGP, and Privacy Guides specifically recommends Stalwart for self-hosted email. www.privacyguides.org
• With OpenPGP + Web Key Directory (WKD), you can make encrypted communication with compatible clients/users substantially easier.
• You can use your own domain, e.g. hello@yourhealthblog.com.
• You can run it on a VPS and keep the mail database, encryption keys, and backups under your control.

The important caveat: self-hosting does not automatically mean end-to-end encrypted email. TLS protects mail while it's transported between servers, but ordinary email sent to Gmail, Outlook, etc. can still ultimately be readable by the recipient's provider. For genuinely sensitive conversations, use PGP or a secure-mail workflow.

Easier alternative: Proton Mail + your domain

If by “my own domain” you mean your own address/domain rather than your own physical server, I would actually choose Proton.

Proton supports custom domains on paid plans, and messages between Proton users are end-to-end encrypted. Proton also provides zero-access encryption for stored mail. proton.me

Proton Mail custom-domain documentation

This is considerably easier to operate than a mail server and is a particularly good choice if you expect readers to email you about potentially sensitive health topics.

If you want a polished self-hosted package: mailcow

mailcow is another strong option. It packages the mail server, webmail, spam/virus protection, DKIM, TLS, administration, and 2FA into one system. docs.mailcow.email

It does require more resources and maintenance: current mailcow documentation recommends at least 6 GB RAM plus 1 GB swap, with 8 GB recommended for a small private installation. docs.mailcow.email

What I'd deploy for your blog

Best balance:

your domain → VPS → Stalwart → encrypted disk → encrypted off-site backups

I'd configure:

1. Dedicated VPS with full-disk/storage encryption where available.
2. Stalwart for SMTP/IMAP.
3. TLS everywhere.
4. SPF + DKIM + DMARC to prevent spoofing and improve deliverability.
5. PGP/WKD for readers who need genuine end-to-end encryption.
6. 2FA for administrative accounts.
7. Encrypted, offline/immutable backups of mail and encryption keys.
8. Separate contact@, privacy@, and editor@ addresses rather than exposing a personal mailbox.
9. Avoid putting sensitive health information into ordinary email unnecessarily.

One especially important point for a health blog: don't treat ordinary email as a HIPAA-style secure communication channel just because your server is encrypted. If readers might submit medical histories, diagnoses, medications, or other sensitive information, I'd create a dedicated secure submission/contact mechanism instead of encouraging them to email those details.

Bottom line:

• Maximum sovereignty: Stalwart self-hosted.
• Maximum privacy with minimal administration: Proton + your domain.
• Best full-featured traditional self-hosted suite: mailcow.

If you tell me your approximate budget (e.g. $5, $10, or $20/month) and whether you're comfortable administering a Linux server, I can recommend a specific architecture and hosting setup.

For a health-focused blog, I’d prioritize privacy, domain ownership, strong account security, and good deliverability over simply “hosting your own mail server.” Running your own server gives you control, but it also creates a large security and maintenance burden (spam reputation, backups, patching, encryption configuration, monitoring).

My recommended options:

Best overall: Proton Mail with your custom domain

Proton Mail

Why it fits a health blog:

• End-to-end encryption between Proton users and zero-access encryption for stored mail. proton.me
• Supports your own domain (for example, hello@yourhealthblog.com). proton.me
• Strong security options:
  • 2FA
  • hardware security keys (depending on account setup)
  • phishing protections
  • SPF/DKIM/DMARC support for domain reputation proton.me
• Good balance between privacy and usability.

Good addresses to create:

• hello@domain.com — public contact
• editor@domain.com — publishing inquiries
• privacy@domain.com — privacy requests
• newsletter@domain.com — mailing list separation
• yourname@domain.com — personal admin account

Potential limitation: Email sent to ordinary Gmail/Outlook users is not automatically end-to-end encrypted unless you use a secure message method or another encryption system. That is a limitation of the email ecosystem, not just Proton. proton.me

Most privacy-maximal: Tuta

Tuta Mail

Choose this if your priority is: “I want the provider to have as little ability as possible to access my mailbox.”

Strengths:

• End-to-end encryption by default.
• Encrypts more mailbox data than traditional email systems, including subject lines and contacts. tuta.com
• Supports custom domains on paid plans. tuta.com
• Strong privacy-oriented design and German data protection environment. tuta.com

Trade-offs:

• Less compatible with traditional email apps and workflows than some competitors. proton.me
• Some health-blog workflows (assistants, CRM tools, newsletter integrations) may require more planning.

Best “normal email experience”: Fastmail

Fastmail

Good if you need:

• excellent email apps
• custom domains
• reliable sending/receiving
• easy integration with other tools

Fastmail is privacy-respecting and ad-free, but it is not designed around provider-inaccessible end-to-end encryption like Proton or Tuta. privacy-decoded.com

My suggested setup for a health blog

Domain registrar

• Use a reputable registrar that supports privacy protection.

Email host

• Start with Proton Mail (best balance).

DNS security
Configure:

• SPF — prevents spoofing
• DKIM — cryptographically signs outgoing mail
• DMARC — protects your domain reputation

These are especially important if you send newsletters. proton.me

Account security

• Enable hardware security keys if possible.
• Use a dedicated password manager.
• Create separate admin and public-facing addresses.

Newsletter separation
Do not send large subscriber campaigns directly from your personal mailbox. Use a privacy-conscious newsletter platform and keep your main mailbox isolated.

My recommendation by scenario

For most independent health bloggers, I would choose Proton Mail + custom domain + SPF/DKIM/DMARC + hardware security key. It gives a strong privacy posture without turning email administration into a full-time job.

For a health-focused blog, I’d recommend Proton Mail with your own domain rather than running your own mail server.

My top pick: Proton Mail + your domain

For example:

hello@yourhealthblog.com
contact@yourhealthblog.com
privacy@yourhealthblog.com

Why I’d choose it:

• Strong encryption: Proton uses end-to-end encryption between Proton users and zero-access encryption for stored mail. You can also send password-protected encrypted messages to people using Gmail, Outlook, etc. proton.me
• Custom domains: Paid Proton plans support addresses on your own domain. proton.me
• Good fit for sensitive health conversations: If readers contact you about personal health experiences, you don't want your email provider's business model or administrators routinely having access to readable inbox contents.
• Security controls: Proton supports 2FA, PGP/OpenPGP, and additional account-security features. proton.me
• Business features: If the blog eventually has multiple contributors, Proton supports organization/user management and custom-domain addresses. proton.me
• Good deliverability setup: You can configure SPF, DKIM, and DMARC for your domain, which is important for preventing spoofing and improving delivery. proton.me

A strong alternative: Tuta

Tuta Mail is arguably the better choice if maximum metadata privacy is more important to you than compatibility.

Tuta provides end-to-end encryption, custom domains on paid plans, open-source clients, and particularly strong encryption of email data. tuta.com

The trade-off is that Proton has better interoperability and broader business/productivity features, including PGP and support for conventional desktop mail clients through Proton Mail Bridge. proton.me

What I would not do

I wouldn't self-host Postfix/Dovecot on a VPS unless you specifically want the administrative responsibility. You'd have to handle:

• spam/phishing filtering
• backups
• server security and patching
• IP reputation and blacklists
• SPF/DKIM/DMARC
• TLS
• encryption at rest
• monitoring and uptime
• mail deliverability

And self-hosting doesn't magically provide end-to-end encryption: ordinary email sent to Gmail, Outlook, etc. still isn't E2EE.

One important health-blog distinction

If you're going to receive actual patient/client health information, email privacy alone isn't enough. You should avoid encouraging readers to send diagnoses, medical records, medications, or other sensitive information through ordinary email unless you've established an appropriate compliance/privacy workflow. In particular, if the blog is associated with a healthcare provider or you're handling regulated health information, the appropriate requirements can be considerably more stringent.

For a typical independent health-information blog, though, my setup would be:

Domain registrar → privacy-conscious DNS → Proton Mail → SPF + DKIM + DMARC → 2FA/security key → separate public contact address

I'd also use an address such as contact@... for public submissions rather than exposing the account you use for administration.

If you tell me whether this is a personal blog, a business/clinic blog, or a blog where readers may submit personal medical information, I can recommend the appropriate setup and security level.

For a health-focused blog, I’d prioritize privacy and encryption without taking on the security burden of running a mail server yourself.

My recommendation: Tuta Mail + your own domain

Tuta is probably the best fit if privacy is the primary requirement.

• Custom domain: You can use addresses such as hello@yourblog.com, with paid plans supporting multiple custom domains. tuta.com
• End-to-end encryption by default: Tuta encrypts email contents, attachments, subject lines, contacts, calendars, and its search index. tuta.com
• Strong privacy architecture: Tuta says it cannot access users' encrypted mailbox contents and stores data on its own servers in Germany. tuta.com
• Encrypted communication with non-Tuta users: You can send password-protected encrypted messages to people using Gmail, Outlook, etc. tuta.com
• Good fit for health-related correspondence: It is specifically marketed for medical/health use and business privacy. tuta.com
• Post-quantum cryptography: Tuta currently uses quantum-resistant algorithms as part of its encryption architecture. tuta.com

Tuta Business

Strong alternative: Proton Mail

Proton is my second choice. It has excellent privacy, custom-domain support, zero-access encryption, and E2EE between Proton users. proton.me

Proton Mail custom domains

I'd choose Proton if you want a more conventional email ecosystem and particularly value compatibility with existing email applications through Proton Mail Bridge. proton.me

What about literally hosting it yourself?

If by "on my own domain" you mean running the mail server yourself, I'd generally not recommend that for a health blog unless you have substantial server/security expertise.

A platform such as mailcow can give you genuine control over your mail infrastructure, with TLS for SMTP/IMAP and automated Let's Encrypt certificate support. docs.mailcow.email

But self-hosting means you become responsible for patching, backups, spam reputation, malware filtering, TLS configuration, authentication, server compromise, IP reputation, and reliable delivery. Also, normal email is not automatically end-to-end encrypted just because your server uses TLS.

Recommended setup

For your use case, I'd do:

Domain registrar → Tuta Business → hello@domain.com, contact@domain.com, privacy@domain.com

Then configure:

1. MFA/passkeys on the Tuta account.
2. SPF, DKIM, and DMARC on your domain.
3. A dedicated contact@ address for reader correspondence.
4. A separate administrative address that isn't publicly advertised.
5. Password-protected E2EE messages when readers need to send genuinely sensitive information.
6. A clear notice telling readers not to email medical records or highly sensitive health information unless you've specifically provided a secure process for doing so.

One important distinction: email encryption doesn't automatically make a health blog HIPAA-compliant. If you're actually collecting protected health information on behalf of a covered entity/business associate, that's a substantially different compliance question.

Bottom line: For a privacy-first health blog, I'd pick Tuta + your existing domain rather than self-hosting. If you specifically want maximum infrastructure control and are comfortable administering Linux/mail systems, then mailcow is the self-hosted route worth considering.

For a health-focused blog, I’d prioritize privacy, domain control, spam resistance, and the ability to protect reader communications. I would generally avoid running your own mail server unless you already manage servers professionally; email hosting has difficult deliverability, abuse, and security maintenance issues. alexi.shsecuremailguide.com

My recommendations:

1. Best overall privacy choice: Proton Mail with your custom domain

Proton Mail

Best for: a health blog where readers may send sensitive questions or personal information.

Strengths

• End-to-end encryption between Proton users and encrypted options for external recipients.
• Zero-access encryption model: the provider is designed so it cannot read encrypted mailbox contents. privacy-decoded.com
• Custom domain support on paid plans. alexi.shsecuremailguide.com
• Good privacy reputation and a broader privacy ecosystem (calendar, storage, VPN, etc.). privacy-decoded.com

Tradeoffs

• Less seamless with traditional email clients unless you use Proton Mail Bridge.
• Some workflows are more locked into Proton’s apps. alexi.shsecuremailguide.com

Good setup for a health blog

• hello@yourdomain.com — general inquiries
• newsletter@yourdomain.com — mailing list
• privacy@yourdomain.com — privacy-related requests
• Use a separate form tool for collecting health-related questions rather than encouraging readers to email medical details.

2. Best usability/privacy balance: Fastmail

Fastmail

Best for: a professional blog where you want email to work like Gmail/Google Workspace without advertising-based services.

Strengths

• Excellent custom-domain support.
• Strong spam filtering and organization.
• Works with normal email clients (IMAP/SMTP).
• Good calendars, contacts, aliases, and workflow tools. alexi.shsecuremailguide.com

Tradeoff

• It is privacy-focused, but it is not a zero-knowledge encrypted mailbox in the same way Proton is. privacy-decoded.com

This is probably the easiest choice if your blog is mostly publishing content, newsletters, partnerships, and reader correspondence that does not contain sensitive health information.

3. Privacy-focused traditional email: Mailbox.org

mailbox.org

Best for: people who want classic email standards plus stronger privacy features.

Strengths

• German jurisdiction.
• Supports standard email protocols.
• Supports PGP workflows for users who want encryption control.
• Includes productivity features. securemailguide.com

Tradeoff

• Less polished than Proton or Fastmail for many users.
• Encryption requires more setup and user awareness. securemailguide.com

I would not recommend self-hosting for this use case

Running your own mail server (for example with Mailcow, Postfix, or similar) gives maximum control, but you become responsible for:

• server security updates
• backups
• spam filtering
• IP reputation
• DKIM/SPF/DMARC configuration
• avoiding blacklists
• uptime monitoring

For a health-focused site, a commercial privacy-focused provider usually gives a better security-to-maintenance ratio. alexi.shsecuremailguide.com

Additional privacy steps I’d use for a health blog

1. Enable domain email authentication
   • SPF
   • DKIM
   • DMARC (start with monitoring, then move toward enforcement)

2. Use separate services for newsletters
   • Keep your private mailbox separate from your subscriber database.
   • Avoid storing health-related reader messages in marketing platforms.

3. Add a clear disclaimer
   • Email is not a secure medical consultation channel.
   • Avoid asking readers to send diagnoses, medical records, or identifiable health details.

4. Use MFA everywhere
   • Hardware security keys are preferable for the main admin account.

5. Register your domain privately
   • Use domain privacy protection where available.

My pick:

• Health education blog with occasional sensitive reader messages: Proton Mail + custom domain.
• Professional blog/newsletter/business workflow: Fastmail + custom domain.
• Technical/privacy enthusiast who wants traditional email standards: Mailbox.org.

For most health-focused bloggers, I’d choose Proton Mail for the inbox and a separate privacy-conscious newsletter platform for subscribers.

For a health-focused blog, I’d recommend Proton Mail with your own domain as the best overall balance of privacy, encryption, usability, and professional email hosting.

My recommendation: Proton Mail + your domain

For example, you could have hello@yourblog.com, contact@yourblog.com, and privacy@yourblog.com hosted by Proton.

Why it fits a health-focused site:

• End-to-end encryption: Proton supports E2EE between Proton users, while incoming mail is stored with zero-access encryption. proton.me
• Custom domains: Paid Proton plans support your own domain. proton.me
• Strong domain security: You can configure SPF, DKIM, and DMARC, which is important for preventing impersonation of your health brand and improving deliverability. proton.me
• Good fit for sensitive correspondence: If readers might send you personal health information, Proton gives you a substantially better privacy posture than conventional hosted email.
• Desktop-client support: Proton Mail Bridge lets you use clients such as Thunderbird, Apple Mail, or Outlook while retaining Proton's encryption architecture. proton.meproton.meproton.me

Proton Mail custom-domain setup

A strong alternative: Tuta Mail

Tuta is arguably the more privacy-maximalist choice. It encrypts the entire mailbox—including subject lines, contacts, and calendars—and says its servers store the data encrypted. It also supports custom domains on paid plans. tuta.comtuta.com

Tuta additionally uses post-quantum cryptography and stores its data in Germany, making it particularly attractive if minimizing provider access to your data is the priority. tuta.com

Tuta Mail

What I wouldn't choose for your priority

Fastmail is excellent traditional email hosting and has strong encryption in transit/at rest, custom-domain support, passkeys, and 2FA. But it doesn't provide native end-to-end encryption in its own apps, instead recommending PGP/S/MIME for E2EE. www.fastmail.com

So I'd rank them:

One important health-specific caveat: if your readers are going to send you identifiable medical/health information, don't assume that "encrypted email" automatically makes your operation HIPAA-compliant or otherwise legally compliant. Your email provider, contracts, data handling, retention, and the way you collect/process information all matter.

For a typical health blog where the goal is "don't expose readers' correspondence unnecessarily, and give them a private way to contact me," I'd choose Proton Mail + a domain registered separately from the email provider, with SPF/DKIM/DMARC and 2FA/passkeys enabled.

For a health-focused blog, I would prioritize privacy, account security, domain reputation, and avoiding accidental exposure of sensitive communications. You probably do not need to run your own mail server (which is difficult to secure and maintain); a privacy-focused hosted email provider is usually the better solution.

Recommended choice: Proton Mail with your custom domain

Best overall fit for a health blog. proton.me

Why:

• End-to-end encryption for Proton-to-Proton messages and zero-access encryption for stored mail. proton.me
• Supports custom domains (for example hello@yourhealthblog.com). proton.me
• Strong privacy reputation and Swiss jurisdiction.
• Supports PGP/OpenPGP, useful if you communicate with clinicians, researchers, or privacy-conscious readers. proton.me
• Good ecosystem if you also want encrypted storage, passwords, calendar, or VPN.

A practical setup:

• hello@domain.com → public contact
• newsletter@domain.com → mailing list
• press@domain.com → media inquiries
• yourname@domain.com → private admin account

Use aliases where possible so your personal inbox is not exposed.

Strong alternative: Tuta Mail

Choose this if your priority is maximum privacy architecture over convenience.

Advantages:

• End-to-end encryption by default.
• Encrypts more mailbox data than traditional email systems, including subject lines and contacts. tuta.comwww.fastmail.com
• Custom domain support on paid plans. tuta.comwww.fastmail.com
• German jurisdiction and GDPR-focused approach. tuta.com

Tradeoffs:

• Less compatible with traditional email clients/workflows than Proton.
• Some integrations may be more limited. proton.me

Best “normal email” experience: Fastmail

Good if you need:

• Excellent search
• Traditional email apps
• Calendars and contacts
• Easy domain management

Fastmail supports custom domains and strong security practices, but it is not end-to-end encrypted in the same way as Proton or Tuta. www.fastmail.com

My recommended stack for a health blog

Domain registrar

• Use a privacy-conscious registrar that supports WHOIS privacy.

Email

• Proton Mail paid plan (best balance)
• Tuta Mail paid plan (maximum privacy)

DNS security
Configure:

• SPF
• DKIM
• DMARC (start with monitoring, then move toward enforcement)

These reduce spoofing and improve deliverability. Proton specifically recommends SPF, DKIM, and DMARC when using custom domains. proton.me

Account protection

• Hardware security key (YubiKey-style) for the admin account
• Password manager-generated password
• Separate admin email not published anywhere

Blog contact forms
Avoid sending form submissions directly into a normal inbox if readers might share:

• medical histories
• symptoms
• medication details
• identifying health information

Instead:

• Add a notice that the blog is not a secure medical communication channel.
• Minimize collected data.
• Consider storing submissions separately with access controls.

My ranking for your use case

1. Proton Mail + custom domain — best overall for a health-focused creator
2. Tuta Mail + custom domain — strongest privacy-first option
3. Fastmail + custom domain — best usability, weaker encryption model

I would avoid self-hosting mail unless you already manage servers professionally; the security burden (spam filtering, patching, TLS configuration, backups, reputation management) is substantial.

For a health-focused blog, I’d recommend self-hosted Stalwart Mail Server if “my own server + strong privacy” is the priority. If you mean “use my own domain but avoid operating a mail server,” I’d choose Proton Mail instead.

Best self-hosted option: Stalwart

Stalwart is particularly interesting because it goes beyond ordinary TLS:

• Encryption at rest: Stalwart can encrypt stored messages using the recipient's OpenPGP public key or S/MIME certificate, meaning an administrator with access to the disk cannot simply read those messages. It supports AES-128 and AES-256 modes. www.stalwart.emailwww.stalwart.emailwww.privacyguides.org
• Strong transport security: It supports TLS plus DANE, MTA-STS and TLS reporting, and can automatically provision certificates through ACME/Let's Encrypt. www.stalwart.email
• Modern security architecture: It's written in Rust, has rate limiting/IP blocking and has undergone security auditing. www.stalwart.email
• Normal email compatibility: It supports SMTP, IMAP and JMAP, so you're not locked into a proprietary client. www.stalwart.email
• Domain authentication: You can configure SPF, DKIM, DMARC and MTA-STS, which is important for a blog's email reputation and protection against spoofing. stalwart.emailstalw.art

A good architecture would be:

Your domain → VPS → Stalwart → encrypted mailbox storage → Thunderbird/another mail client

For particularly sensitive correspondence, I'd use OpenPGP end-to-end encryption between you and trusted recipients. TLS alone does not provide end-to-end encryption—it protects email while it is being transported, whereas encryption with the recipient's public key can protect the message itself.

Privacy Guides also specifically recommends Stalwart for self-hosted email and highlights its encrypted-message storage and OpenPGP/WKD capabilities. www.privacyguides.org

Easier alternative: Proton Mail + your domain

If you don't actually need to control the server, Proton Mail is probably the better practical choice.

You can use you@yourdomain.com on a paid Proton plan, while Proton provides zero-access encryption for externally received mail and end-to-end encryption between Proton users. proton.me

The trade-off is that Proton hosts the infrastructure. That's substantially easier and probably more reliable than self-hosting, but it doesn't give you the same level of server-side control.

What I'd choose for your blog

One important health-related consideration: don't treat ordinary email as inherently HIPAA-secure just because your server uses encryption. If your blog will receive identifiable patient/client health information, that's a substantially different compliance problem; you'd want to design the intake process so readers aren't encouraged to send sensitive medical information by ordinary email.

If you want to actually self-host, I can also give you a concrete Stalwart setup for your domain—including VPS specs, DNS records, TLS, DKIM/DMARC, backups, encryption-at-rest, and a privacy-oriented configuration. stalwart.emailstalw.art

For a health-focused blog, I’d recommend Proton Mail with your own domain rather than running your own mail server.

My pick: Proton Mail + your domain

It gives you a strong balance of privacy, encryption, reliability, and low maintenance:

• Custom domain: You can use addresses such as hello@yourblog.com; paid Proton plans support custom domains. proton.meproton.me
• Zero-access encryption: Proton says stored mail is encrypted so Proton itself cannot access the contents. proton.meproton.me
• End-to-end encryption: Messages between Proton users are automatically E2EE. For people using Gmail/Outlook/etc., you can send password-protected encrypted messages rather than relying on ordinary email encryption. proton.me
• Good domain authentication: Set up SPF, DKIM, and DMARC on your domain to reduce spoofing and phishing. Proton documents all three as part of custom-domain setup. proton.me
• Less operational risk: You don't have to maintain an SMTP server, spam reputation, TLS configuration, backups, patching, etc.—all particularly important for a public-facing health site.

For a health blog, I'd also avoid putting actual patient/client health information into ordinary email. E2EE between Proton accounts is strong, but email to someone on Gmail or another provider isn't automatically end-to-end encrypted. For sensitive correspondence, use Proton's password-protected encrypted-email mechanism or, preferably, a dedicated secure intake/portal system.

Strong alternative: Tuta

Tuta Mail is arguably even more privacy-oriented. It encrypts the mailbox, contacts, calendars, and subject lines, supports custom domains, and uses post-quantum-resistant cryptography. Its servers are based in Germany. tuta.com

I'd choose Tuta if maximum privacy/metadata protection is more important than integrations and conventional email compatibility.

One important distinction

If by “host email on my own domain” you mean actually operate the mail server yourself, I wouldn't recommend that unless you already administer mail infrastructure. Self-hosting gives you control, but it also makes you responsible for security, backups, spam filtering, IP reputation, uptime, encryption, and incident response. For a small health-focused publication, that tradeoff usually isn't worthwhile.

Recommended setup:
yourblog.com → privacy-focused registrar/DNS → Proton Mail → hello@yourblog.com, contact@yourblog.com, etc., with SPF + DKIM + DMARC enabled and 2FA/passkeys on the administrator account.

If the blog will collect health questions, patient stories, or other potentially sensitive submissions, I'd go one step further and separate the public contact email from a genuinely secure submission system.