Page Comparison

Note

title	GDPR NOTICE

We used to snapshot the that rendered the blacklist reason.

However, as of 25th may 2018, when the data protection law changed the history of personal integrity, we no longer store this kind of content. It might sound strange that we do not store spam that works like a proof for why e-mail has been blacklisted. It also normally helps system administrators (especially those who administers email services) to trace the source of spam. But to protect the receivers part data, the mail spam storage project has been abandoned.

Panel

title	Table of contents

Table of Contents

API description, development and DNSBL docs

Child pages (Children Display)

first	5

...

In the DNSBLv3-API a new set of permissions are assigned to the DNSBL. Normally, no permissions are required (to list blacklisted hosts).

Tip

title	Requesting permissions?

The special permissions need to be requested manually via support@tornevall.net

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 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

ip	Array with 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:

and bitmasked flag-per-ip

The bitmask flags mentions here

Example:

Code Block

language	js
title	Do blacklist

{
	"ip": {
		"10.10.10.10": 64
	},
	"type": "dnsbl"
}

Response Look:

Response parameters (status) described

success	The insertion ID
address	The address that was update or inserted
state	Defines if the request already has the address blacklisted or if it was updated. Answers can be new or update.
arpaDelegations	A list of DNS-records that was registered or updated
flag	The flag of the blacklisted address

Code Block

language	js
title	Do blacklist

{
	"ip":"1.2.3.4",
	"flags":64,
	"type":"dnsbl"
"dnsblResponse": {
		"status": [{
			"success": "1934699",
			"address": "10.10.10.10",
			"state": "new",
			"arpaDelegations": [
				"10.10.10.10.dnsbl.tornevall.org"
			],
			"flag": "64"
		}]
	}
}

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",
}

...

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.

...

Versions Compared

Old Version 17

New Version Current

Key