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