What factors go into determining whether an IP is a threat, and how often is this reviewed?
One of the problems I have with most public intel (don't care if it's FireHOL, Crowdstrike, Alienvault or US-CERT) is that inevitably some GoDaddy (for example) site gets used by an APT and so a GoDaddy IP makes it onto a public blacklist, flagged as being abusive. But a billion other sites also share that IP on that host (or it gets reassigned, as in AWS) which leads to a deluge of false positives anytime anyone else happens across it by means of a legitimate site. Some of these IPs remain blacklisted for years despite any malicious infrastructure long being dismantled.
Do you add any value by mitigating this, or do you just suck down the same public blacklists every other product uses?
You make a valid point. A number of VPN providers for example use GCE/AWS/Softlayer to host their services. And these IPs do get reassigned.
One of the ways we mitigate this is by limiting the age of IP addresses in our lists to a maximum of 30 days. If an IP address hasn't been reported to have been responsible for malicious behavior for a period of 30 days it shouldn't be in our lists.
We're also mulling adding an is_cloud_provider field to the threat response object.
Why is is_anonymous = true for a tor relay? Why are relays and exit nodes given the same flag? As a tor relay operator, I anticipate this being misused, like so many before it, to arbitrarily block all tor relays by people who don't know or care how tor works.
Hi f2n, thank you for raising this concern. is_tor and is_anonymous are true for any and all nodes on the Tor network. I'd love to hear more about your concerns, please send me an email at jonathan at ipdata dot co
I've always had good luck with Maxmind's local database [1] offering. It bewilders me how many companies today create SaaS offerings and refuse to offer on-prem versions. It's like they intentionally want to avoid customers with serious needs (speed and security being the most common need for on-prem) who are willing to pay serious amounts of money.
Hi, unfortunately we don't. However performance is very important to us which is why we have 11 endpoints around the world. And average ~65ms response times see status.ipdata.co.
This is definitely really cool and something I imagine myself using for future projects. The price points are very reasonable and the website is very usable. One question I have though is what best practices do you recommend for how one can protect against IP address spoofing.
The data is updated as often as every 15 minutes, though we aggregate all those changes over the course of an hour. Are you interested in only the threat data? We have been considering making it possible to query for individual fields
One of the few services that geoip's my VPN correctly to germany. Too many of them pick it on France and I get shown lots of ads I don't understand. And no threat either (some blacklist me for sitting on an OVH network).
I tried sharing your page on FB messenger to a friend who is interested in this kind of APIs, but Messenger blocked it...man I hate this blacklisting crap...back to IRC it is.
Hi sphix0r, yes. First off we only store logs from user requests for 24hrs and only for analytics. Otherwise our GDPR compliance is still something we're perfecting but something we believe we're already on the right side of.
Jonathan's been doing a great job of ipdata.co! I'd like to also shout out to my own service https://ipinfo.io here though, where we've recently launched new plans that include company details, carrier details, and IP type - we have a custom classifier that labels each IP as isp, business, or hosting, which can be really useful for a bunch of use cases. Here's sample output from the pro plan:
[+] [-] jstarfish|8 years ago|reply
What factors go into determining whether an IP is a threat, and how often is this reviewed?
One of the problems I have with most public intel (don't care if it's FireHOL, Crowdstrike, Alienvault or US-CERT) is that inevitably some GoDaddy (for example) site gets used by an APT and so a GoDaddy IP makes it onto a public blacklist, flagged as being abusive. But a billion other sites also share that IP on that host (or it gets reassigned, as in AWS) which leads to a deluge of false positives anytime anyone else happens across it by means of a legitimate site. Some of these IPs remain blacklisted for years despite any malicious infrastructure long being dismantled.
Do you add any value by mitigating this, or do you just suck down the same public blacklists every other product uses?
[+] [-] jonathan-kosgei|8 years ago|reply
You make a valid point. A number of VPN providers for example use GCE/AWS/Softlayer to host their services. And these IPs do get reassigned. One of the ways we mitigate this is by limiting the age of IP addresses in our lists to a maximum of 30 days. If an IP address hasn't been reported to have been responsible for malicious behavior for a period of 30 days it shouldn't be in our lists.
We're also mulling adding an is_cloud_provider field to the threat response object.
[+] [-] f2n|8 years ago|reply
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] Reedx|8 years ago|reply
I've been using Cloudflare to detect TOR, but couldn't find a good way to detect proxies/etc.
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] jonathan-kosgei|8 years ago|reply
And append it to https://api.ipdata.co. For example; https://api.ipdata.co/185.10.68.114
[+] [-] 47|8 years ago|reply
[+] [-] meritt|8 years ago|reply
[1] https://www.maxmind.com/en/geoip2-databases
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] hangonhn|8 years ago|reply
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] nickreese|8 years ago|reply
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] zaarn|8 years ago|reply
Good work!
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] orliesaurus|8 years ago|reply
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] logronoide|8 years ago|reply
[+] [-] unmonk|8 years ago|reply
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] logronoide|8 years ago|reply
I think I will use it in https://apility.io, a service that competes at some point with this.
[+] [-] Mediumium|8 years ago|reply
Small suggestion : 1500 api request for free and 2500 api requests for 10€.
I think it's a huge leap for pricing, either reduce the requests for free user or reduce de price / increase the requests for the first payed plan.
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] 256cats|8 years ago|reply
[+] [-] 0x0|8 years ago|reply
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] sphix0r|8 years ago|reply
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] PedroSena|8 years ago|reply
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] edf13|8 years ago|reply
[+] [-] jonathan-kosgei|8 years ago|reply
[+] [-] coderholic|8 years ago|reply
[+] [-] always_good|8 years ago|reply
You made the same post during OP's last Show HN: https://news.ycombinator.com/item?id=15881463
I also wonder how mature a project has to be before it seems sheepish to "Show HN".
[+] [-] jonathan-kosgei|8 years ago|reply