Alternatives to AbuseIPDB
Other Threat intelligence vendors we measure, sorted by how much they publish that AbuseIPDB does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from AbuseIPDB on at least one criterion we measured for both. Public transparency score, not a product or security rating.
AbuseIPDB has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and AbuseIPDB does not” is the one that closes them.
| Vendor | Score | Publishes, and AbuseIPDB does not | AbuseIPDB publishes, and they do not | |
|---|---|---|---|---|
| Dataminrdataminr.com | 70/100 | 7 Data processing agreement, Subprocessor list, Certifications named, +4 | 1 Public pricing | Compare |
| Feedly Threat Intelligencefeedly.com | 48/100 | 7 Subprocessor list, Status page with history, Certifications named, +4 | 2 Data location stated, Public pricing | Compare |
| Cywarecyware.com | 39/100 | 5 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +2 | 2 Data location stated, Public pricing | Compare |
| Intezerintezer.com | 48/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 1 Public pricing | Compare |
| Anomalianomali.com | 43/100 | 4 Status page with history, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 Public pricing | Compare |
| Cyblecyble.com | 22/100 | 4 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 2 Data location stated, Public pricing | Compare |
| GreyNoisegreynoise.io | 30/100 | 3 Uptime SLA with a figure, HTTPS enforced with HSTS, Named privacy contact | 1 Public pricing | Compare |
| Intel 471intel471.com | 26/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 2 Data location stated, Public pricing | Compare |
| Recorded Futurerecordedfuture.com | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Public pricing | Compare |
| Censyscensys.com | 39/100 | 2 Status page with history, HTTPS enforced with HSTS | nothing | Compare |
| IPinfoipinfo.io | 39/100 | 2 Data processing agreement, security.txt (RFC 9116) | nothing | Compare |
| Pulsedivepulsedive.com | 39/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | nothing | 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.