Endpoint
Description
Get information about listed ip-addresses. A POST request is required for this to work (officially). However, one (unsupported) command does the same: /3.0/dnsbl/request/ip/<address>
Parameters
| Parameter | Description |
|---|---|
| ip | Address list (arrays allowed) |
Examples
{"ip":["44.11.12.77","18.33.14.30"]}
"dnsblResponse": [
{
"ip": "44.11.12.77",
"typebit": "84",
"discovered": "2017-12-16 16:06:03",
"typestring": "torexit",
"deleted": "2018-06-30 05:00:18",
"lastchange": "2018-06-30 05:00:18"
},
{
"ip": "18.33.14.30",
"typebit": "84",
"discovered": "2017-11-03 20:53:54",
"typestring": "phishing",
"deleted": "0000-00-00 00:00:00",
"lastchange": "2017-11-03 20:53:54"
}
]
As you can see, one of the hosts above are also marked as deleted by the deleted-string. This means that is has been removed from the DNS service and therefore won't shop up in a DNS request. This kind of flags is used to show - in removal tools - that the host has been listed but is now removed.
Looking for networks (CIDR-scanning)
If you need to look for ip-addresses, based on netmasking with a CIDR smaller than a /8, you can set an ip to look up for example this
{
"ip":["44.11.0.0/16"]
}
It is not impossible that this example block actually returns something and it's only your imagination (or your network) that sets the search limit here. This feature does not exist in APIv2.
Exceptions
When the API find no blacklisted hosts
As of APIv3, exceptions are thrown in the response interface if nothing is found as listed. This should make it easier to detect errors together with unlisted addresses, instead of looking for empty response arrays. This is what's thrown, when this occurs.
{
"response": [],
"errors": {
"code": "404",
"success": "",
"faultstring": "Nothing found as listed"
}
}