Alternatives to Yandex 360
Other Email hosting vendors we measure, sorted by how much they publish that Yandex 360 does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from Yandex 360 on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Yandex 360 has 8 gaps in what we could measure: Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Yandex 360 does not” is the one that closes them.
| Vendor | Score | Publishes, and Yandex 360 does not | Yandex 360 publishes, and they do not | |
|---|---|---|---|---|
| Fastmailfastmail.com | 30/100 | 3 Public pricing, HTTPS enforced with HSTS, No third-party tracking before consent | 3 Data processing agreement, Data location stated, Named privacy contact | Compare |
| Migadumigadu.com | 30/100 | 3 Status page with history, Public pricing, No third-party tracking before consent | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | Compare |
| Gandigandi.net | 30/100 | 2 Status page with history, Certifications named | 2 Data processing agreement, Named privacy contact | Compare |
| Hushmailhushmail.com | 30/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, security.txt (RFC 9116), Named privacy contact | Compare |
| df.eudf.eu | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data processing agreement, Data location stated | Compare |
| All-Inklall-inkl.com | 22/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | Compare |
| Biohostbiohost.de | 22/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | Compare |
| Grommuniogrommunio.com | 22/100 | 2 Public pricing, No third-party tracking before consent | 3 Data processing agreement, Data location stated, Named privacy contact | Compare |
| mailbox.orgmailbox.org | 22/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 3 Data processing agreement, Data location stated, Named privacy contact | Compare |
| Mailfencemailfence.com | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 4 Data processing agreement, Data location stated, security.txt (RFC 9116), +1 | Compare |
| Posteoposteo.de | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 4 Data processing agreement, Data location stated, security.txt (RFC 9116), +1 | Compare |
| Netcupnetcup.de | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 4 Data processing agreement, Data location stated, security.txt (RFC 9116), +1 | 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.