To clarify, the original post from myself is more ARIN related and scraping of ARIN data. The incoming cold contacts from the ipv4-broker-spammer came to ARIN POCs for an ASN with presence only in the USA.
On Fri, Oct 13, 2023 at 8:23 AM t...@pelican.org <t...@pelican.org> wrote: > On Friday, 13 October, 2023 16:04, "Laura Smith via NANOG" < > nanog@nanog.org> said: > > > RIPE could do the same. And some might argue that it is easier for RIPE > because > > all we are asking is for a valid abuse contact, so its not like Nominet > who have > > to verify e.g. registrant company ID numbers. > > They do. In previous lives, I've regularly been on the receiving end of > assorted audit requests from RIPE, some of which are to do with contact > details in the DB (particularly when they find unreachable ones), and some > of which are confirming that number resources are still in use by the > organisation and for the purpose for which they were issued. > > I think the original complaint was that RIPE don't act (or less so than > ARIN) to block or otherwise deal with people who are mining the DB for > contacts, despite that being an incentive to put "real" data in the DB - > not than that they don't push for accurate data in the DB. > > Thanks, > Tim. > > >