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