SUCCESS message when not blacklisted about iptell HOT 9 CLOSED

What sort of response would you expect?

The implementation is parallel (async.map). Or are you looking for something else specifically? We could cache the results for some time. That would help on the subsequent results.

Are you aware of an IP that each RBL blocks by design? This would help in testing.

from iptell.

At least in the olden days we'd blacklist 127.0.0.2 as one of the test IPs on RBLs. I'd be surprised if that's not still common.

from iptell.

For example

$ dig +short -t any 2.0.0.127.spamsources.fabel.dk
"Blocked http://www.spamsources.fabel.dk/ip/127.0.0.2"
127.0.0.2

from iptell.

@abh Thanks! Works perfectly. :)

from iptell.

@eamonnscu Just figured out what might have caused that delay you experienced. We are running the API on Heroku. By default they hibernate services. This means if the service hasn't been used for some time, it has to start it on request. Are you experiencing that 7s delay consistently?

from iptell.

good catch @bebraw.

from iptell.

the first request seemed quite slow (a few seconds- maybe 5) from chrome.

then it started to load fast...

Chriss-MacBook-Air:Downloads chris$ time curl http://api.iptell.io/v1/blacklisted/184.173.163.234
[]
real 0m0.660s
user 0m0.007s
sys 0m0.009s
Chriss-MacBook-Air:Downloads chris$ time curl http://api.iptell.io/v1/blacklisted/184.173.163.234
[]
real 0m0.319s
user 0m0.009s
sys 0m0.005s
Chriss-MacBook-Air:Downloads chris$ time curl http://api.iptell.io/v1/blacklisted/184.173.163.234
[]
real 0m0.289s
user 0m0.011s
sys 0m0.005s
Chriss-MacBook-Air:Downloads chris$ time curl http://api.iptell.io/v1/blacklisted/184.173.163.234
[]
real 0m0.344s
user 0m0.011s
sys 0m0.005s
Chriss-MacBook-Air:Downloads chris$ time curl http://api.iptell.io/v1/blacklisted/184.173.163.234
[]
real 0m0.302s
user 0m0.011s
sys 0m0.006s

from iptell.

as for the success message, maybe something saying that no blacklist entries were found. (right now it's an empty set)

from iptell.

Thanks!

from iptell.