Transparency alternatives to Red Sift
Other Email security vendors we measure, sorted by how much we found at them and not at Red Sift. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from Red Sift on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Red Sift has 2 gaps in what we could measure: No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Red Sift” is the one that closes them.
| Vendor | Score | Found there, not found at Red Sift | Found at Red Sift, not found there | |
|---|---|---|---|---|
| URIportsuriports.comSee also Transparency alternatives to URIports | 70/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 3 Subprocessor list, Status page with history, Named privacy contact | Compare |
| Retarusretarus.comSee also Transparency alternatives to Retarus | 26/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | Compare |
| Riottryriot.comSee also Transparency alternatives to Riot | 65/100 | 1 security.txt (RFC 9116) | 2 Data processing agreement, Status page with history | Compare |
| Hoxhunthoxhunt.comSee also Transparency alternatives to Hoxhunt | 61/100 | 1 security.txt (RFC 9116) | 2 Public pricing, Named privacy contact | Compare |
| Abnormalabnormalsecurity.comSee also Transparency alternatives to Abnormal | 52/100 | 1 security.txt (RFC 9116) | 2 Data processing agreement, Public pricing | Compare |
| Darktracedarktrace.comSee also Transparency alternatives to Darktrace | 35/100 | 1 security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Keepnet Labskeepnetlabs.comSee also Transparency alternatives to Keepnet Labs | 26/100 | 1 security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| Phishedphished.ioSee also Transparency alternatives to Phished | 26/100 | 1 security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| Trustifitrustifi.comSee also Transparency alternatives to Trustifi | 19/100 | 1 security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Hornetsecurityhornetsecurity.comSee also Transparency alternatives to Hornetsecurity | 17/100 | 1 security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Mimecastmimecast.comSee also Transparency alternatives to Mimecast | 17/100 | 1 security.txt (RFC 9116) | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | Compare |
| SOC Radarsocradar.ioSee also Transparency alternatives to SOC Radar | 17/100 | 1 security.txt (RFC 9116) | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | 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.