Alternatives to Migadu
Other Email hosting vendors we measure, sorted by how much they publish that Migadu does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from Migadu on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Migadu has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Migadu does not” is the one that closes them.
| Vendor | Score | Publishes, and Migadu does not | Migadu publishes, and they do not | |
|---|---|---|---|---|
| Stalwartstalw.art | 39/100 | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | 3 Status page with history, No third-party tracking before consent, Named privacy contact | Compare |
| Yandex 360yandex.com | 35/100 | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | 3 Status page with history, Public pricing, No third-party tracking before consent | Compare |
| Gandigandi.net | 30/100 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | 3 Public pricing, No third-party tracking before consent, Named privacy contact | Compare |
| Fastmailfastmail.com | 30/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Status page with history, Named privacy contact | Compare |
| Hushmailhushmail.com | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Status page with history, No third-party tracking before consent, Named privacy contact | Compare |
| df.eudf.eu | 26/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Public pricing, No third-party tracking before consent | Compare |
| mailbox.orgmailbox.org | 22/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Status page with history, Public pricing, Named privacy contact | Compare |
| OVH Mailovh.com | 19/100 | 2 Data location stated, security.txt (RFC 9116) | 3 Status page with history, No third-party tracking before consent, Named privacy contact | Compare |
| Stratostrato.de | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Status page with history, Public pricing, No third-party tracking before consent | Compare |
| Infomaniakinfomaniak.com | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Status page with history, Public pricing, No third-party tracking before consent, +1 | Compare |
| Netcupnetcup.de | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 4 Status page with history, Public pricing, No third-party tracking before consent, +1 | Compare |
| All-Inklall-inkl.com | 22/100 | 1 HTTPS enforced with HSTS | 2 Status page with history, Public pricing | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.