As a reminder, our removal tools is up and running at https://www.tornevall.net/removal/. Please, do NOT comment delisting requests since the comment fields are normally used as a spamming resource.
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.
Our removal tools that works agains DNSBL v5.0 is finally released. It’s up and it has been tested both with ipv4 and ipv6-connections, so now we’re ready to release it in public too.
And if you still need manual support, you may want to take a look at http://docs.tornevall.net/x/OIBu as usual.
There is an ongoing project with TorneLIB which has a standalone project for handling our API. It’s not ready for release, but you can review the upcoming script at the dev-site here!
If you recently contacted us about removal and you seem to be relisted, the release of version 5 may be the cause, and the fact that some hosts has not been properly updated in both our databases.
FraudBL is, since june 22, an active resolver. Tornevall Networks has in active for tests and currently we’ve seen a positive result of the activation. More information about bitmasking will in short get updated at http://docs.tornevall.net/x/AoA_/. In short, we will also activate the new default database for dnsbl.tornevall.org.
You can still contact firstname.lastname@example.org for blacklisting support.
FraudBL is currently up and running and while we are typing this post, we are collecting spam from ”phishing sites”. As we are counting, approximately 1200 hosts are flagged ”phishing” in our database. In short, this database will get a zone update so we can start using it. What we are actually waiting for is dnsbl.tornevall.org and the last migration steps.
Our primary network link went down yesterday. It has been reported, but it seems like it will take a little bit longer to fix this time. However, we’re not completely down, since we switched over to our backup route while we are waiting.
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…
We have’nt updated for a while, so it may be time for that now. The work is in progress but due to lack of time in private, it has taken longer than expected. But we’re still here, still taking DNSBL requests by firstname.lastname@example.org (with a SLA based on quick response time). Our SSL certificates are getting updated and currently, we’re on A-level (referring to sslabs tests). The new platform is still only available offline, but since this text is written with the help of that platform, there is some kind of confirmation of the progress,
In the meantime, you may want to have a look at this link, if you need further support. The forum is currently low-frequently updated, so we need a kickstart with it.But it’s still a community so it may be a good idea to take a look there.
Our documentation site is also up and running here.
To be continued…