Alternatives to Retarus
Other Email security vendors we measure, sorted by how much they publish that Retarus does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from Retarus on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Retarus has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, Notice before subprocessors change, Named privacy contact. The column “publishes and Retarus does not” is the one that closes them.
| Vendor | Score | Publishes, and Retarus does not | Retarus publishes, and they do not | |
|---|---|---|---|---|
| Red Siftredsift.com | 83/100 | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Hoxhunthoxhunt.com | 74/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 1 No third-party tracking before consent | Compare |
| Abnormalabnormalsecurity.com | 61/100 | 4 Subprocessor list, Status page with history, Notice before subprocessors change, +1 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| KnowBe4knowbe4.com | 52/100 | 4 Status page with history, Public pricing, Uptime SLA with a figure, +1 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| dmarciandmarcian.com | 48/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | 4 Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | Compare |
| Valimailvalimail.com | 48/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | 3 Data location stated, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Pauboxpaubox.com | 48/100 | 3 Status page with history, Public pricing, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Cofensecofense.com | 39/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 4 Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | Compare |
| Sendmarcsendmarc.com | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Egressegress.com | 39/100 | 2 Data processing agreement, Named privacy contact | 3 Certifications named, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| MailRoutemailroute.net | 35/100 | 2 Public pricing, Named privacy contact | 3 Certifications named, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| PowerDMARCpowerdmarc.com | 35/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Data location stated, No third-party tracking before consent, security.txt (RFC 9116) | 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.