Originally posted on Updated Two-Factor Authentication with RBLTracker
Your account security is extremely important to us here at RBLTracker. Since our initial inception, we’ve supported two-factor authentication using the Clef application, which provided an easy-to-use two-factor authentication, and single sign-on application.
With the recent news that Clef will be shutting down its services in early June (you can read all about it on the Clef blog), we’ve opted to remove support for it early, and implement an alternative two-factor authentication option using TOTP (Time-Based One-Time Passwords), a standard that won’t be going anywhere anytime soon.
TOTP uses an algorithm to compute a one-time password, based on a shared secret and the current time. One benefit of TOTP, is that the 6-digit authentication token that is generated automatically rolls over with time, which dramatically reduces the susceptibility to phishing schemes.
There are many freely available TOTP clients, but RBLTracker recommends the Google Authenticator application, available for free, for Android, iOS, and Blackberry devices. You can learn more about it here:
Two-factor authentication is available today, and can optionally be enabled on any account on the RBLTracker system. For a complete tutorial on setting up two-factor authentication, see the Setting up Two-Factor Authentication guide.
It’s been a few weeks since I launched a new service I’m involved in, and so far the take-up rate has been extremely encouraging.
CheckMail is an email address verification service. Put simply, you give us an email address, and we’ll tell you if it’s a valid, working, email address or not. You can bulk-validate a CSV or Excel file with your email addresses, or you can integrate our solution into your lead generation process using our API.
So far we’ve had a great take-up rate using our API, which is our primary focus for the CheckMail service. Customers can get up and running quickly with the CheckMail API libraries for Node.js, PHP, Python, and Ruby.
We maintain multiple geographically load balanced instances of the CheckMail API, in six different locations throughout the world, to ensure the fastest response times possible for all our customers.
Why Use CheckMail?
- Increase Conversion Rates – Increase conversation rates and the ROI of your campaigns, by focusing your efforts on leads that have been confirmed to be real, working email addresses.
- Protect Your Reputation – Avoid needlessly sending emails to bad, broken, or misspelled addresses, which reduces your exposure to Spamtraps and black lists.
- International Support – CheckMail has full IDN support for email addresses and domains. Whether the address is email@example.com, jöns@example.com, or even 若望@例如.中国, CheckMail can verify it.
- Cloud-Based SaaS Pricing – No software to install, and no upgrade or licensing fees. You’re always using the newest version of the CheckMail product, all for a competitive pay-per-use price, which scales with usage.
Interested? Sign up for email address verifications today, and receive 100 free verifications to get you started!
I’ve released version 1.4.3 of the PEAR Net_DNS2 library- this release is primarily just bug fixes.
You can install it now through the command line PEAR installer:
pear install Net_DNS2
Or, you can also add it to your project using composer:
composer require pear/net_dns2
- fixed an issue when looking up . or com., when using the strict_query_mode flag.
- fixed a bug in the caching logic where I was loading the content more than once per instance, when really I only need to do it once.
- changed the Net_DNS2::sock array to use the SOCK_DGRAM and SOCK_STREAM defines, rather than the strings ‘tcp’ or ‘udp’.
- fixed a bug in the Net_DNS2_Header and Net_DNS2_Question classes, where I was using the wrong bit-shift operators when parsing some of the values. This only became apparent when somebody was trying to use the CAA class (id 257); it was causing this to roll over to the next 8 bit value, and returning 1 (RR A) instead of the CAA class.
- fixed a bug that occurs when a DNS lookup request times out, and then the same class is reused for a subsequent request. Because I’m caching the sockets, the timed out data could eventually come in, and end up being seen as the result for a subsequent lookup.
- fixed a couple cases in NSAP.php where I was comparing a string to an integer.