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