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