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