Page tree

Versions Compared

Key

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

...

Example URL: https://api.tornevall.net/2.0/dnsbl/islisted/255.255.255.252 (Still free to use)

There is also a more detailed rest call that can be done by, for example https://api.tornevall.net/2.0/dnsbl/ip/bulk/255.255.255.255

Warning
titleAPI Rest URLs and usage

Information about this coming very soon

...

TorneLIB contains a smaller independent library to keep track of listed hosts and may be included in projects that requires the use of the DNSBL/FraudBL. This project is about to replace a lot of things that has been "alive" (barely?) since 2006.

You can download review the standalone library here: at https://dev.tornevall.net/sources/dnsbl/tornevall_dnsbl.php (Note: This library extension follows our develop development trunk, so it may be incomplete from time to time).

How to use this library extension

Code Block
languagephp
titleResolving in it's simplest form
require_once(__DIR__ . "/autoload.php");
$dnsbl = new \TorneLIB\TorneLIB_DNSBL();
if ($dnsbl->isListed($testaddr)) {
    /* Actions to take against this host */
}

Other methods

...

isListed()

...

resolveBlacklist()

...

An array with strings defined in TORNEVALL_DNSBL_BITS.
The constants are listed below.

...

getBitArray()

...

getBlVersion()

...

isBit()

...

The TORNEVALL_DNSBL_BITS-class also have another method callable from public called isBit().
Let's say that you have the bitmask value 80, which represents the two bits BIT_ABUSE (64) and BIT_SPAM (16), you can ask this function if they are present. 

Code Block
languagephp
titleisBit()-method
$bitValue = 80;
$BitClass = new \TorneLIB\TORNEVALL_DNSBL_BITS();
$BitClass->isBit();
if ($BitClass->isBit(self::BIT_SPAM, $bitValue)) { /* Do something here */ }
if ($BitClass->isBit(self::BIT_ABUSE, $bitValue)) { /* Do something here */ }

This method is calling isBit() in the TORNEVALL_DNSBL_BITS-class.

What is happening in this component?

Jira
serverTornevall Networks
columnssummary,type,created,updated,status,resolution
maximumIssues20
jqlQuerycomponent = PHPCli-TorneLIB_DNSBL ORDER BY status ASC, resolution DESC, "Internal priority", priority DESC, updated DESC
serverIdef1f2374-e58a-319f-9d38-10348dbac859

...

Where to read about the DNSBL Libraries

TorneLIB_DNSBL (PHP)

rbl-extension

The former name of the DNSBL at sourceforge is named rbl-extension and can be found here. The plans is to also upgrade that "platform".

...

The public development repo for this project can be reach through svn://svn.tornevall.net/dnsbl/standalone/trunk and the current (and also last version of branch 1.0) can be reached at svn://svn.tornevall.net/dnsbl/standalone/branches/1.0. The trunk will soon get patched with TorneLIB-DNSBL. 

 

Historical summary

In the beginning there was spamming. The spamming took it's place on a swedish forum, hosted by a swedish TV-channel, inspired by an international project called "Big Brother". The year was actually 2006 and trolls were highly active on this forum. In the same time, there was an irc-server that received a load of attacks by proxies.

At this moment, there was a project on the big internet called BOPM (Blitzed Open Proxy Monitor) that has special clients checking on connecting clients to that irc server. Tornevall Networks started to think of migrating a similar solution into web spaces. The problem, that made a huge difference between the IRC and WWW-protocol was the fact that on IRC, you made one connection and then one check against a DNS Blacklist. If it was blacklisted as an open proxy, it got k-lined, akilled in any other form: banned. This was not possible with HTTP-connections, since a check would take place each time a client connected to a website. The idea in this case, was to cache the resolving, into a local storage since DNS-servers otherwise could be overloaded with queries (depending on how DNS caching was made).

Somewhere in may 2006, this project started and the first extension released was actually the rbl-extension at sourceforge, together with an extension for the CMS tool e107 and vBulletin. After this year, 2006, no more suprises happened. Only maintenance jobs. Recently someone has realized that the old projects has became quite obsolete. Deprecation of the old project from 2006 was initiated somewhere between december 2015 and june 2016.