|Table of Contents|
Check the bottom of this page to get more information about migrations to version 5 or here to view the DNSBL Project dashboard.
TorneAPI v3.0 is coming up with a new request interface, which is configured via the TorneAUTH Control panel. Currently, the control panel is very simple and the only purpose of it, is to create the required API key that is required to do extended requests. For example, adding and delisting spamhosts. If you only need the resolving controls, you should consider using the DNS lookup instead of the API lookup as it is much faster than API requests.
If you still think that the API is the right way to go, continue reading at the new API description docs.
The current environment of TorneAUTH is pointing at v3.0 (not to be mixed with the API release). If you are willing to take the risk, the test servers for TorneAUTH (unstable) is located at https://auth.tornevall.com (version 4) and https://auth.tornevall.nu (version 3 development).
APIv2 is deprecated
What is a DNSBL?
A DNS-based Blackhole List (DNSBL, Real-time Blackhole List or RBL), is a means by which an Internet site may publish a list of IP addresses, in a format which can be easily queried by computer programs on the Internet. As the name suggests, the technology is built on top of the Internet DNS or Domain Name System. DNSBLs are chiefly used to publish lists of addresses linked to spamming. Most mail transport agent (mail server) software can be configured to reject or flag messages which have been sent from a site listed on one or more such lists (Source)
We are regularly scanning new proxies that are reported to us and we're also trying to keep updated with the "Tor"-network proxies, a network that forgets that anonymity can be a problem when we are speaking abuse.
dnsbl.tornevall.org: Default zone
opm.tornevall.org: Added 1 june 2016 (Deprecation as of 30 june 2013 was reverted)
bl.fraudbl.org: Added 22 june 2016
RBL Bitmasking Data
IP address has been reported (As this bit has no real actual effect and rather is a false positive, it will be deprecated in short)
Meaning: The ip has been reported from a third party application, honeypot, but may not necessarily be confirmed by our local sweepers (this is for proxies)
Deprecating from march 2017
IP has been confirmed as working proxy.
When FraudBL is used, this mask confirms the host as fraudible (Servers used for phishing, fraud, etc)
Active since June 2016
Will update soon
As this bitvalue has no meaning (since it only flags that nothing happens while trying to connect to it, this will change shape soon (Deprecated: timeout)
June 2016: E-Mail spammer
Active since June 2016
IP is tested and is fully functional but there is a second entry point (meaning this ip is not the same as the one that has been used by the user"), or the address is an exit node in TOR-network
IP is marked as "abusive". Primary used to point out spam or attacks through webforms, forum, telnet, etc.
IP has a different anonymous-state (web-based proxies, like anonymouse, etc)
|Follows all bitmasks as dnsbl.tornevall.org generates.|
|Special bitmasking in the fraudbl zone is upcoming|
wl.tornevall.org - whitelisting system [PLANNED ONLY]
This status is set by the auto whitelisting system, after manual inspections
This status is set by the webservice removal system
This status is set when removal has been made manually, through support
The FraudBL Project
FraudBL has just been started as a separate project - for the moment you can reach the site at https://fraudbl.org. FraudBL - Explained has been added here at the docs (from fraudbl.org), for your convenience.
FraudBL is a separate project, which lists mail that contains all kinds of phising. However, dnsbl.tornevall.org is covering FraudBL too so you actually don't need to resolve against both domains unless you don't want another scoring on the FraudBL content. Since dnsbl.tornevall.org collects all kinds of spam, the scoring is normally lower rated than the phising mail.
More information about the scoring can be found at DNSBL for Spamfilters.
We are currently working on a complete migration to a new system. Here, you can find the status of that project.
Older versions from 2006 are following TornevallWEB versioning (1.x-4.x).
Why does the project take time?
The complexity of some of our functions are described in
Project status chart