The RBLTracker service was upgraded to version 1.12 today, which includes the following new features:
Custom Check Frequency
Customers subscribed to the Ultimate package can now adjust the frequency of their host checks, using a simple drop-down list from the Profile -> Settings section:
At the moment, customers can select from a 6 hour window, to a 48 hour window. Finer grained controls will likely be added in future releases.
We’ve made some very basic changes to the API service:
- Replaced all instances of the term “blocked” with “listed”. The “blocked” terminology is still available, but customers should migrate to the new terminology as soon as possible, as it will be deprecated in future releases.
- The matched RBLs have been added to the response data. This includes the RBL matched, the RBL website, and the RBL output from DNS.
- The API version number is now included in the response object.
An updated API document is available from the API Access section of the RBLTracker portal.
Customers can now add their Twitter screen name to their account as notification contacts. RBLTracker will send a direct message to your Twitter account anytime a host matches (or based on your scheduling settings:
Customers must follow the @rbltracker Twitter account with the same Twitter handle in order to received direct messages. We also cannot send URLs in direct messages, due to limitations on the Twitter platform- hopefully this is something they will correct in the future.
If you have any questions or comments about any of these new features, please let us know @ email@example.com
This evening, we’ve released a new version of the RBLTracker service, which includes all sorts of new features, including:
The custom RBL feature lets you add custom RBLs and URIBLs to your account, which RBLTracker does not normally check.
If you have a paid or in-house RBL that you’d like to use, you can add it here, and centralize your monitoring with RBLTracker, and take advantage of our automated checks, and alerting functionality.
Yandex Safe Browsing Support
RBLTracker now has support to monitor the Yandex Safe Browsing database, alongside the Google Safe Browsing database.
The Google and Yandex Safe Browsing databases include lists of website domains that may be dangerous to visitors, because they are suspected of phishing or malware.
The Google Safe Browsing service is already built-in to both the Chrome and Firefox web browsers, the two most popular web browsers on the internet. If your website is compromised because of an outdated WordPress or Drupal installation, your visitors will receive a warning, telling them that YOUR website is dangerous and should be avoided.
A full list of changes included in this release are available below. Any questions or comments, please let us know @ firstname.lastname@example.org
Release version 1.11
- Added support for monitoring the Yandex Safe Browsing database.
- Added support for custom RBLs and URIBLs that the RBLTracker system does not normally monitor, for example, paid or internal RBLs.
- Added support to download invoices from the billing section of the portal. Customers can also add more detailed billing information through the Profile section of the web portal.
- Added additional pricing options for customers with more than 1000, 2500, and 5000 hosts using the Ultimate package.
- Added an option for customers to delete their accounts.
I’ve released version 1.3.2 of the PEAR Net_DNS2 library- you can install it now through the command line PEAR installer:
pear install Net_DNS2
Download it directly from the Google Code page here.
Or, you can also add it to your project using composer.
- added support for the EUI48 and EUI64 resource records (RFC7043).
- fixed how we handle the return values from socket select() statements; this wasn’t causing a problem, but it wasn’t quite right.
- added some error messaging when the socket times out).
- before we cache the data, unset the rdata value; this was causing some JSON errors to be generated, and we don’t need the data anyway.
Now selecting which RBLs to use with RBLTracker is even easier than before!
As of today, customers can create custom RBL Profiles which let them select from over 60 RBLs, 20 URIBLs, and the Google Safe Browsing database, and then apply this profile to multiple hosts, removing the need to customize each host separately.
Customers can even mark one of their RBL Profiles as the “default” profile, and it will automatically be used anytime a new host is added to the system- either manually, or using the bulk host loader.
How Does This Work?
From the RBL Profiles section, give the new profile a unique name, and click “Add RBL Profile” to select which RBLs to use:
Then either edit a host and select this new RBL Profile from the drop down, or select the RBL profile when adding a new host:
RBLTracker is a fully automated RBL monitoring service, which checks your IP addresses and website domains against the most frequently used real-time black lists (RBLs) and Safe Browsing Databases.
Don’t waste time by manually checking all your servers yourself- RBLTracker does it automatically, without any user intervention.