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