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