...
Method | URL/data | The parameter | Expected response |
---|---|---|---|
HTTP POST | https://api.tornevall.net/2.0/dnsbl/ip/ | ||
HTTP POST variables | ?bulk[]=ipaddr1&bulk[]=ipaddr2 | bulk[]=ipAddr | Arrayed (or not arrayed by only using bulk=ipAddr) request should return information about the current blacklisted ip (if it is blacklisted). To return fingerprints about the ip address, you could add ipAddr|e, where e stands for extended information. To add or delete a host in the blacklist, with specific permissions additional parameters was used: |a|<bitValue> for adding the address with a bit value (described here), or |d for deletion. Additional parameters (with permissions) could be used to purge (p) content. |
...
Method | URL | Information | Data (POST parameters) | Expected response | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
HTTP POST | https://api.tornevall.net/3.0/dnsbl/ or | HTTP POST has the same role as HTTP GET but with post parameters. Supports IPv6. | URL-encoded or JSON-formatted:
This example is the same for the rest of examples in this table. | Is ip listed? | ||||||||||||||||||||||||||||||||
HTTP PUT | https://api.tornevall.net/3.0/dnsbl/ | Insert or update ip address |
Example:
The bitmask flags mentions here Example:
Response Look: Response parameters (status) described
| |||||||||||||||||||||||||||||||||
HTTP DELETE | https://api.tornevall.net/3.0/dnsbl/ | Delist (delete/remove) ip address | Example:
|
...
The default "type" used in some of the examples above is using the standard registration behaviour. It is simply just "dnsbl". As fraudbl.org is using the same flagset (see DNSBLv5: About the DNS Blacklist Project and usage), normally we don't need to know anything else than this. Adding a host with the flagid 4 (phishing) will also automatically update the fraudbl tables with proper data.
...