AbuseIPDB has been overhauled and is under new management!

Welcome to the new AbuseIPDB.com. As of April 2016, AbuseIPDB has been acquired by Proud Development, LLC and Marathon Studios Inc., a technology company based in Pennsylvania, USA. Here's all you need to know:

We have been working hard over the past few weeks to develop v2.0 of AbuseIPDB, which features a completely overhauled and modern codebase as well as new features for logged-in users, better UX, and additional security.

The upgrade is a work in progress, so we are relying on your feedback to help us! Please drop us a line if you notice any errors or bugs, or have feature suggestions or comments.

Upcoming Features

Over the coming months, we plan to roll out handful of new tools to AbuseIPDB, including:

  • Fail2Ban Module

    We are working on building a free plugin for Fail2Ban that will allow system administrators to report and blacklist IPs to AbuseIPDB dynamically in real-time.
  • Improved Documentation

    We are planning to add code examples for using the AbuseIPDB API in a variety of languages.
  • Premium Features

    We are working on developing premium features that we will introduce to paid users, including access to updated blacklists of IPs recently engaged in malicious activities and unlimited access to the API. However, we are committed to continuing to provide all of the services currently available on AbuseIPDB for free!

Contribute to AbuseIPDB!

We're a small team of developers and system administrators, and we hope that AbuseIPDB can continue to be a valuable tool for our peers all over the world. We are always looking for coders to help us improve the project!

If you have feature suggestions, questions, comments, bug fixes or want to contribute, please contact us. We look forward to hearing from you.

~The AbuseIPDB Team

** This Document Provided By AbuseIPDB **
Source: https://www.abuseipdb.com