Transparency alternatives to SOC Radar
Other Email security vendors we measure, sorted by how much we found at them and not at SOC Radar. 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, Data location stated, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at SOC Radar” is the one that closes them.
| Vendor | Score | Found there, not found at SOC Radar | Found at SOC Radar, not found there | |
|---|---|---|---|---|
| Red Siftredsift.comSee also Transparency alternatives to Red Sift | 83/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| MailRoutemailroute.netSee also Transparency alternatives to MailRoute | 61/100 | 5 Data processing agreement, Data location stated, Uptime SLA with a figure, +2 | 2 Certifications named, security.txt (RFC 9116) | Compare |
| URIportsuriports.comSee also Transparency alternatives to URIports | 70/100 | 4 Data processing agreement, Data location stated, No third-party tracking before consent, +1 | nothing | Compare |
| Riottryriot.comSee also Transparency alternatives to Riot | 65/100 | 4 Subprocessor list, Data location stated, Notice before subprocessors change, +1 | nothing | Compare |
| SoSafesosafe-awareness.comSee also Transparency alternatives to SoSafe | 65/100 | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | 1 security.txt (RFC 9116) | Compare |
| Hoxhunthoxhunt.comSee also Transparency alternatives to Hoxhunt | 61/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 1 Public pricing | Compare |
| Abnormalabnormalsecurity.comSee also Transparency alternatives to Abnormal | 52/100 | 4 Subprocessor list, Status page with history, Notice before subprocessors change, +1 | 1 Public pricing | Compare |
| Cofensecofense.comSee also Transparency alternatives to Cofense | 39/100 | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | 4 Public pricing, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Pauboxpaubox.comSee also Transparency alternatives to Paubox | 48/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| dmarciandmarcian.comSee also Transparency alternatives to dmarcian | 35/100 | 3 Data processing agreement, Status page with history, Named privacy contact | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Supedsuped.comSee also Transparency alternatives to Suped | 43/100 | 2 Data processing agreement, Data location stated | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Retarusretarus.comSee also Transparency alternatives to Retarus | 39/100 | 2 Data location stated, No third-party tracking before consent | 1 Public pricing | 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.