Page Comparison

Panel

title	Table of contents

Table of Contents

API description, development and DNSBL docs

Child pages (Children Display)

first	5

...

Permission flag	Description
allow_cidr	The usage of CIDR-blocks are normally not permitted by the DNSBL API, in more functions than listing them. This permission also opens up for usage in DELETE/UPDATE cases (in our local e-mail requests where support sometimes cover CIDR-block removals, this would help a lot). However, adding data with CIDR and different flags might be a problem (this permission does not exist in the API yet)
allow_cidr_update	Setting that partially allows CIDR-block updates for the DNSBL (there migt me limitations linked to this permission - see the documentation for this information) *Current limitations: Not* lower *larger than a /24. This permission is also, currently, limited for internal use.*
can_purge	Special ability to purge hosts instead of marking them deleted in the database
dnsbl_update	Standard DNSBL ability to update data in the DNSBL (dnsbl.tornevall.org and bl.fraudbl.org)
fraudbl_update	Extended ability to handle fraudbl-commerce (this is not the regular bl.fraudbl.org resolver)
global_delist	Global delisting permission (can use as delisting service for visitors)
local_delist	Local delisting permission (server can delist self)
overwrite_flags	When sending new or updated data to DNSBL, clients can only add more flags to the host. This feature makes it possible to overwrite old flags Not yet implemented

...

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.

FIngerprints are used to make API requesters get more information about the

...

Method

URL

Information

Data (POST parameters)

Expected response

HTTP POST

https://api.tornevall.net/3.0/dnsbl/

or

https://api.tornevall.com/3.0/dnsbl/request/ip/1.2.3.4

HTTP POST has the same role as HTTP GET but with post parameters. Supports IPv6.

URL-encoded or JSON-formatted:

Code Block
// simple json {"ip":"1.2.3.4"} // simple http post &ip=1.2.3.4 // multiple json {"ip":["1.2.3.4", "5.6.7.8"]} // multiple http post ip[]=1.2.3.4&ip[]=5.6.7.8

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

Address to insert or update in DNSBL

<type>

What to update (defaults to dnsbl)

This information will update

<flags>

The bitmast flags mentions here

Example:

Code Block

language	js
title	Do blacklist

{
	"ip":"1.2.3.4",
	"flags":64,
	"type":"dnsbl"
}

HTTP DELETE

https://api.tornevall.net/3.0/dnsbl/

Delist (delete/remove) ip address

Example:

Code Block

language	js
title	Do blacklist

{
	"ip":"1.2.3.4",
}

...

Versions Compared

Old Version 16

New Version 17

Key