December 2013 - anti-abuse-wg

Re: [anti-abuse-wg] Who owns 195.82.146.0 - 195.82.147.255?
by Oleg Kolesnikov 18 Dec '13

18 Dec '13

Oh, thank you. That was The Idea! I checked: not valid phone number. (It looks like in Seychelles in phone number must be 1 digit more.) Oleg Kolesnikov NPO ADCI 2013/12/18 Jørgen Hovland <jorgen(a)hovland.cx> > I don't understand why you would think that. There is nothing obvious. > Anyway, I have many times tried to call the listed number when I suspect > there is something wrong. Sometimes they do answer, but also sometimes they > dont/fake number. > > > > > > At 13:38 18/12/2013 (UTC), Oleg Kolesnikov wrote: > > This person obviously not from this company: > > descr: Avtomatizatsiya Business Consulting Ltd. > country: RU > > person: Le Mon Grinua > address: Seychelles, Victoria Mahe > > > And do hosting-provider may have only "P.O. Box" ? > (In this case he cannot be formally notified.) > > > Oleg Kolesnikov > NPO ADCI > > > 2013/12/18 Jørgen Hovland <jorgen(a)hovland.cx<http://mail?p=compose&to=jorgen@hovland.cx> > > > >> Hello, >> >> person: Le Mon Grinua >> address: Seychelles, Victoria Mah�, P.O.Box 981 >> phone: +248 621 100 >> >> Cheers, >> >> At 13:06 18/12/2013 (UTC), Oleg Kolesnikov wrote: >> >> Who owner of IPs 195.82.146.0 - 195.82.147.255 ? >> >> Avtomatizatsiya Business Consulting Ltd. >> have no address, no email [torrents.ru domain is NOT DELEGATED] >> >> Therefore we have no any contact data for this "owner". >> >> >> Oleg Kolesnikov >> NPO ADCI >> > >

2 1

Update on "abuse-c:" coverage in RIPE Database
by Johan Åhlén 18 Dec '13

18 Dec '13

Dear Colleagues, We have now reached the end of the extended period for Phase 1 of the abuse-c project. This means that we will start the process of setting the "abuse-c:" attribute automatically for members where it is missing. For this we will use the publicly listed contact information as described in the implementation plan: https://labs.ripe.net/Members/kranjbar/implementation-details-of-policy-201… Currently, 65.8% of the IPv4 allocations have the "abuse-c:" attribute, and by size the coverage is 74.4%. We will now move into Phase 2, where we will ask PI and ASN resource holders to provide abuse contact information. We will have a simplified form available as well as improved documentation on how to do the update in the RIPE Database using the standard mechanisms. Current IPv4 PI coverage is 7.7% of all PI assignment, and by size the coverage is 13.8% Here are the latest stats: -------- NETWORK NUMBERS: Total number of IPv4 allocations listed: 21,605 Number of IPv4 allocations covered with "abuse-c": 14,219 or 65.8% of IPv4 allocations Total number of IPv4 PI assignments listed: 28,250 Number of IPv4 PI assignments covered with "abuse-c": 2,170 or 7.7% of IPv4 assignments Total number of IPv6 allocations listed: 6,474 Number of IPv6 allocations covered with "abuse-c": 4,282 or 66.1% of IPv6 allocations Total number of IPv6 assignments: 1,593 Number of IPv6 assignments covered with "abuse-c": 231 or 14.5% of IPv6 assignments Total number of objects: 57,922 (IPv4: 49,855 / IPv6: 8,067) Number of objects covered with "abuse-c": 20,902 or 36.1% (IPv4: 32.9% / IPv6: 55.9%) -------- IPv4 NETWORK SIZES: Total size of IPv4 allocations listed: 595,025,920 Size of IPv4 allocations covered with "abuse-c": 442,600,448 or 74.4% Total size of IPv4 PI assigned listed: 169,504,824 Size of IPv4 PI assigned covered with "abuse-c": 23,426,416 or 13.8% Total size of listed IPv4 addresses: 764,530,744 Size of listed IPv4 addresses covered with "abuse-c": 466,026,864 or 61.0% In our last update, the coverage of IPv4 allocations, by size, was 56.8%. Today it is 74.4% -------- LIR NUMBERS: LIRs with "abuse-c:": 4,243 LIRs without "abuse-c:": 5,541 If you have any questions about theses figures, please feel free to contact us. Kind regards, Johan Åhlén Assistant Manager, Database RIPE NCC

3 5

Who owns 195.82.146.0 - 195.82.147.255?
by Oleg Kolesnikov 18 Dec '13

18 Dec '13

Who owner of IPs 195.82.146.0 - 195.82.147.255 ? Avtomatizatsiya Business Consulting Ltd. have no address, no email [torrents.ru domain is NOT DELEGATED] Therefore we have no any contact data for this "owner". Oleg Kolesnikov NPO ADCI

2 1

Automatic IP -> abuse email address mapping
by Olaf van der Spek 15 Dec '13

15 Dec '13

Hi, I hope this is the right list for such a question. How does one map an IP address to an abuse email address in an automated way? I assume scripts exist, but I haven't found any. Does everyone roll their own? -- Olaf

13 38

Recommendations for ISPs
by Brian Rak 09 Dec '13

09 Dec '13

Are there detailed instructions for datacenters about how they should be creating abuse-c records? I've been in contact with a datacenter that has one generic abuse-c contact for their organization, but then each individual network has some remarks saying 'please contact this email address instead'. If you email their general abuse email, they tell you to check WHOIS and email the address in the comments. This completely breaks the RIPE abuse contact finder, as well as my scripts to automatically send abuse emails. They don't seem to see the problem with this, so I was hoping for some decent documentation I could show them about it. How should this generally be handled for network providers with lots of reassigned subnets? Am I right in believing this pretty much defeats the purpose of the abuse-c record?

2 1