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