Transparency alternatives to Dataminr
Other Threat intelligence vendors we measure, sorted by how much we found at them and not at Dataminr. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from Dataminr on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Dataminr has 4 gaps in what we could measure: Status page with history, Public pricing, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Dataminr” is the one that closes them.
| Vendor | Score | Found there, not found at Dataminr | Found at Dataminr, not found there | |
|---|---|---|---|---|
| Feedly Threat Intelligencefeedly.comSee also Transparency alternatives to Feedly Threat Intelligence | 48/100 | 2 Status page with history, security.txt (RFC 9116) | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Censyscensys.comSee also Transparency alternatives to Censys | 39/100 | 2 Status page with history, Public pricing | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | Compare |
| IPinfoipinfo.ioSee also Transparency alternatives to IPinfo | 39/100 | 2 Public pricing, security.txt (RFC 9116) | 6 Subprocessor list, Certifications named, Uptime SLA with a figure, +3 | Compare |
| Pulsedivepulsedive.comSee also Transparency alternatives to Pulsedive | 39/100 | 2 Public pricing, No third-party tracking before consent | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | Compare |
| Recorded Futurerecordedfuture.comSee also Transparency alternatives to Recorded Future | 22/100 | 2 Status page with history, security.txt (RFC 9116) | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | Compare |
| Validinvalidin.comSee also Transparency alternatives to Validin | 19/100 | 2 Public pricing, No third-party tracking before consent | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | Compare |
| Anomalianomali.comSee also Transparency alternatives to Anomali | 43/100 | 1 Status page with history | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | Compare |
| Flashpointflashpoint.ioSee also Transparency alternatives to Flashpoint | 30/100 | 1 Public pricing | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | Compare |
| Cyblecyble.comSee also Transparency alternatives to Cyble | 22/100 | 1 security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | Compare |
| ZeroFoxzerofox.comSee also Transparency alternatives to ZeroFox | 17/100 | 1 Status page with history | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | Compare |
| AbuseIPDBabuseipdb.comSee also Transparency alternatives to AbuseIPDB | 9/100 | 1 Public pricing | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | Compare |
| Team Cymruteam-cymru.comSee also Transparency alternatives to Team Cymru | 4/100 | 1 security.txt (RFC 9116) | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | 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.