Versions Compared

Old Version 19

changes.mady.by.user Thomas Tornevall

Saved on

compared with

New Version Current

changes.mady.by.user Thomas Tornevall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Note
titleGDPR 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.

...

MethodURL/dataThe parameterExpected response
HTTP POSThttps://api.tornevall.net/2.0/dnsbl/ip/

HTTP POST variables?bulk[]=ipaddr1&bulk[]=ipaddr2bulk[]=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

...

MethodURLInformationData (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 PUThttps://api.tornevall.net/3.0/dnsbl/Insert or update ip address


ipArray with ip address
<ipAddress>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
languagejs
titleDo blacklist
{
	"ip": {
		"10.10.10.10": 64
	},
	"type": "dnsbl"
}

Response Look:

Response parameters (status) described

successThe insertion ID
addressThe address that was update or inserted
stateDefines if the request already has the address blacklisted or if it was updated. Answers can be new or update.
arpaDelegationsA list of DNS-records that was registered or updated
flagThe flag of the blacklisted address


Code Block
languagejs
titleDo blacklist
{
	"dnsblResponse": {
		"status": [{
		"ip	"success": "1934699",
			"address": "110.210.310.410",
			"flagsstate":64 "new",
			"typearpaDelegations": [
				"10.10.10.10.dnsbl.tornevall.org"
			],
			"flag": "64"
		}]
	}
}



HTTP DELETEhttps://api.tornevall.net/3.0/dnsbl/Delist (delete/remove) ip address

Example:

Code Block
languagejs
titleDo 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.

...