Transparency alternatives to SoSafe
Other Email security vendors we measure, sorted by how much we found at them and not at SoSafe. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from SoSafe on at least one criterion we measured for both. Public transparency score, not a product or security rating.
SoSafe has 5 gaps in what we could measure: Status page with history, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at SoSafe” is the one that closes them.
| Vendor | Score | Found there, not found at SoSafe | Found at SoSafe, not found there | |
|---|---|---|---|---|
| URIportsuriports.comSee also Transparency alternatives to URIports | 70/100 | 3 No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change | 2 Subprocessor list, Named privacy contact | Compare |
| Hoxhunthoxhunt.comSee also Transparency alternatives to Hoxhunt | 61/100 | 3 Status page with history, security.txt (RFC 9116), Notice before subprocessors change | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| Abnormalabnormalsecurity.comSee also Transparency alternatives to Abnormal | 52/100 | 3 Status page with history, security.txt (RFC 9116), Notice before subprocessors change | 3 Data processing agreement, Data location stated, Public pricing | Compare |
| Red Siftredsift.comSee also Transparency alternatives to Red Sift | 83/100 | 2 Status page with history, Notice before subprocessors change | nothing | Compare |
| Riottryriot.comSee also Transparency alternatives to Riot | 65/100 | 2 security.txt (RFC 9116), Notice before subprocessors change | 1 Data processing agreement | Compare |
| MailRoutemailroute.netSee also Transparency alternatives to MailRoute | 61/100 | 2 Uptime SLA with a figure, Notice before subprocessors change | 2 Subprocessor list, Certifications named | Compare |
| KnowBe4knowbe4.comSee also Transparency alternatives to KnowBe4 | 39/100 | 2 Status page with history, Uptime SLA with a figure | 3 Data processing agreement, Subprocessor list, Data location stated | Compare |
| Retarusretarus.comSee also Transparency alternatives to Retarus | 39/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | Compare |
| Pauboxpaubox.comSee also Transparency alternatives to Paubox | 48/100 | 1 Status page with history | 2 Data processing agreement, Subprocessor list | Compare |
| Cofensecofense.comSee also Transparency alternatives to Cofense | 39/100 | 1 Notice before subprocessors change | 4 Subprocessor list, Public pricing, Certifications named, +1 | Compare |
| Darktracedarktrace.comSee also Transparency alternatives to Darktrace | 35/100 | 1 security.txt (RFC 9116) | 3 Data processing agreement, Subprocessor list, Public pricing | Compare |
| dmarciandmarcian.comSee also Transparency alternatives to dmarcian | 35/100 | 1 Status page with history | 4 Subprocessor list, Data location stated, Certifications named, +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.