Reply to comment:

Anonymous
<div class="content legacycomment"> <p> &nbsp; </p> <p> On the Database Working Group and Anti-Abuse Working Group mailing lists we received some questions we answered about the Abuse Finder tool. Here they are in Q &amp; A style: </p> <p> &nbsp; </p> <p> <strong> Q </strong> :&nbsp; <em> I personally would prefer scriptable stuff (anything that generates&nbsp;text output that may be scripted) Any hope for that ? </em> </p> <p> &nbsp; </p> <p> <strong> A </strong> :&nbsp;The &quot;Abuse Finder&quot; form actually uses an extension to the RIPE Database Query API, which is implemented in the form of a RESTful Web Service. </p> <p> The API allows you to write script against this search tool and responses can be received in either XML or JSON format for easy parsing. </p> <p> &nbsp; </p> <p> We will be updating the API documentation soon, but in the meantime you could try clicking the XML and JSON icons next to the response from the &quot;Abuse Finder&quot; form to see the original response from the web service. </p> <p> &nbsp; </p> <p> <strong> Q </strong> :&nbsp; <em> It would be helpful, if its noted in the output from wich object or field&nbsp;the abuse email address was extracted from (e.g. admin-c, tech-c, remarks,&nbsp;abuse-field also)&nbsp;so output could look like: </em> </p> <p> <em> <br type="_moz" /> <br /> </em> </p> <p class="rteindent1"> <em> admin-c: noc@tester.de </em> </p> <p class="rteindent1"> <em> abuse-email: abuse@tester.de </em> </p> <p class="rteindent1"> <em> <br type="_moz" /> <br /> </em> </p> <p> <em> so that one can decide, wich one is really relevant for their own needs. </em> </p> <p> &nbsp; </p> <p> <strong style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> A </strong> :&nbsp;We did think about applying some weighting to the email addresses&nbsp;returned. However, the abuse handling data is not structured within the&nbsp;RIPE Database. There are many places the abuse handling email can be&nbsp;put. This depends on where the network administrator thinks is the most&nbsp;appropriate place. It could be in an IRT object. Or in the admin-c of&nbsp;the maintainer of the INETNUM object. Because it is very subjective, one&nbsp;address is no more valuable or important than another. In most cases you&nbsp;are unlikely to receive a long list of email address options. So the&nbsp;actual objects they came from is less important. </p> <p> &nbsp; </p> <p> <strong style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> Q </strong> :&nbsp; <em> What are the exact [query] limits?&nbsp;Is there a way of raising the limits for special cases (we maintain our&nbsp;own spam blacklist and do send about 30.000 reports, where there are&nbsp;about 5.000 to 8.000 reports originate from the RIPE region) daily <br /> </em> </p> <p> &nbsp; </p> <p> <strong style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> A </strong> :&nbsp;One of the main reasons for developing this tool is to reduce the need&nbsp;for users to query for personal data objects. In which case limits&nbsp;become less relevant. With the current data structure we cannot yet&nbsp;totally remove this need. Many abuse email addresses are contained in&nbsp;remarks, some of which are within personal data objects. We return links&nbsp;to the objects that contain remarks that may hold such an email address. </p> <p> &nbsp; </p> <p> If the tool does not return any &quot;abuse-mailbox:&quot; email addresses you&nbsp;will need to follow these links to the suggested objects with remarks.&nbsp;By pointing to those objects that have such remarks this tool avoids the&nbsp;need for users to directly query for all personal data objects referenced. </p> <p> &nbsp; </p> <p> <strong> Q </strong> :&nbsp; <em> How can the finder be tested via other protocols [then just a webpage]? </em> </p> <p> &nbsp; </p> <p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> <i> <b> <br /> </b> </i> </p> <div> <strong style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> A </strong> :&nbsp;The back end web service can be accessed via any HTTP client library. The response is available in XML or JSON. Please refer to the <a href="http://labs.ripe.net/content/ripe-database-api-documentation"> API Documentation </a> for further details. <p> &nbsp; </p> </div> <p> &nbsp; </p> </div>