IP-DB is a free, public-interest service. The people on this page improved it directly — by reporting a bug, testing a release, running a sensor, or getting a record corrected. Their work is named in the software's release notes, not just here.
In alphabetical order; the order means nothing else. Names are shortened for privacy — anyone who would rather appear in full can write us one line and we will update it the same day.
When a finding turns into a release, the finder is named in the release notes. The entries below appear in the notes shipped with the downloadable kits.
Every HTTP decoy sent an "http:profile" tag on top of the connection it had already recorded under the profile name, so one visit appeared twice under two labels. Found by a sensor operator who compared his own journal with what he had configured.
--status built the panel address from the web host the command line does not have, instead of the name the install reports. In the same place, an install with no secret of its own derived one before the cache directory was known, so the token in the printed panel link was refused by the gate.
The binary search could skip a row when the probe landed exactly on its first byte, so roughly a third of listed addresses came back as "not listed". The report also produced --verify, which reads the kit's whole index back through the same search.
A wrong score, a bad record, or a defect in one of the kits: one email is enough. Every confirmed finding is named in the release notes.
The honeypot sensor records the attacks aimed at your own server and feeds the pool. One command to install, and the data shows up on your own dashboard too.
If you believe an address is listed by mistake, we review the record, remove it, and look at the source that sent it. That is a contribution too.
Even a small detail can turn into a release. Write to us; we look the same day.
Our free, open-source honeypot sensor waits on ports your server does not use and reports the scanners and attackers that connect to a shared blocklist.
Thousands of CVEs are published every week; a handful matter. The bulletin collects what actually started being exploited that week, plus the critical vulnerabilities worth your time, in one email.
