Endpoint

/3.0/dnsbl

Description

Update or create a new entry in the DNS Blacklist.

Syntax

The format of this PUT request can be made in several ways. The base look of the data you send is this:

{
    "ip":["44.11.12.77"]
}

Just as in the regular lookup case DNSBLv5APIv3: getListed (POST). However, be careful with the variant described at the other doc. Putting data into the system DO support multiple addresses. This however changes the requirements of the input data object. In the old API, adding data without a bitmasked value would set the value 64 to the host (IP_ABUSE_NO_SMTP). In the APIv3 service this kind of syntax is not allowed, since we prefer to get proper bitmask values on each added host (in case they are different to each other):

{
    "ip":["44.11.12.77","18.33.14.30"]
}

To be more specific with what kind of address you're adding, you can also format your input syntax like this:

{
	"ip":{"44.11.12.77":"32"}
}

Sending this data into the DNSBL, will add the IP-address 44.11.12.77 with the bitmask value of 32.

In fact, this kind of syntax therefore supports adding multiple hosts in one call:

{
	"ip": {
		"44.11.12.77":"32",
		"18.33.14.30":"104"
	}
}

In this call, you're adding the first host with the flag IP_SECOND_EXIT and the second with multiple flags (102 = IP_ABUSE_NO_SMTP, IP_SECOND_EXIT, IP_CONFIRMED and IP_PHISHING).

When this document is written, the output response is not completed yet - so the below example might change over time.

{
	"dnsblResponse": {
		"status": [{
				"address": "44.11.12.77",
				"arpa": "77.12.11.44",
				"state": "new",
				"arpaDelegations": [],
				"flag": "32"
			},
			{
				"address": "18.33.14.30",
				"arpa": "30.14.33.18",
				"state": "new",
				"arpaDelegations": [],
				"flag": "99"
			}
		]
	}
}