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