Currently there's a few steps left before we can release the new portal system (as shown via the test site at https://www.tornevall.com) and the new portal configurator (Test site located at https://auth.tornevall.com). The old platform for handling DNS Blacklists became deprecated as the development of NetCURL (https://www.netcurl.org) have been highly upgraded to fit other (ecommerce) needs. The behaviour of netcurl is backward compatible, but the DNS blacklist and portal software really needed a facelift anyway. I've been looking for a platform that I can handle easier than the self built, and got stuck into a million of alternatives. However, the forum platform is still there, since there are too many posts and history behind. So those parts can't be replaced (yet). Besides, if everything goes well, there might be no need of doing so. So what's left before a release? Actually, TorneAPI (3.0) is ready to go live and the applications built in the API is also very dynamic. As I proceed more things will be added to it and currently, the big focus is the DNS Blacklist, FraudBL and NETFILTER.
As a reminder, our removal tools is up and running at https://dnsbl.tornevall.org/removal/. This method works much faster today, than sending requests to the support mail - and the SLA for manual removals has therefore been changed to a bit lower than before. The tools are there for you. More information about DNSBL could also be found here.
The "Tor Exit Node scanner" has been down for a while due to the long unconvenient upgrade made. It is however re-instated with a small bonus: From now on, the ExitNode-scanner will be self-sanitized and hosts discovered as exit nodes will automatically get removed as soon as the official ExitNode-list (https://check.torproject.org/exit-addresses) is updated.
For three years ago (june 2013) we decided to remove the substructure opm.tornevall.org, from the DNSBL. Statistics, however, shows that opm are still in use. And in fact traffic seems to increase, from those resolvers. They are therefore reinstated, even if there will be double entries of each blacklisted host. Our honeypot have also begun to catch e-mail on a new level. Messages containing traces of phishing and fraud will be flagged differently from the regular lookups. This refactoring and migrating to the new system are not finished yet, so bit-flags are not considered yet. However, our new domain for phishing - FraudBL - may be useful here. And do not forget: As long as the migration is not finished, we will continue remove your blacklisted hosts manually, with as high SLA as possible. In that case, we still use the support address email@example.com To be continued...