Alternatives to IPinfo
Other Threat intelligence vendors we measure, sorted by how much they publish that IPinfo does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 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 “publishes and IPinfo does not” is the one that closes them.
| Vendor | Score | Publishes, and IPinfo does not | IPinfo publishes, and they do not | |
|---|---|---|---|---|
| Dataminrdataminr.com | 70/100 | 6 Subprocessor list, Certifications named, Uptime SLA with a figure, +3 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Feedly Threat Intelligencefeedly.com | 48/100 | 6 Subprocessor list, Status page with history, Certifications named, +3 | 3 Data processing agreement, Data location stated, Public pricing | Compare |
| Anomalianomali.com | 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.com | 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.com | 48/100 | 3 Certifications named, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Public pricing, security.txt (RFC 9116) | Compare |
| GreyNoisegreynoise.io | 30/100 | 3 Uptime SLA with a figure, HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Public pricing, security.txt (RFC 9116) | Compare |
| Intel 471intel471.com | 26/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Data location stated, Public pricing, +1 | Compare |
| Cyblecyble.com | 22/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Data location stated, Public pricing | Compare |
| Censyscensys.com | 39/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| Pulsedivepulsedive.com | 39/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| Recorded Futurerecordedfuture.com | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Public pricing | Compare |
| Group-IBgroup-ib.com | 13/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Data location stated, Public pricing, +1 | 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.