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