A
anneslogUsede
Guest
There used to be kiddypr0n here. It be gone, now.
Last edited:
inetnum: 212.117.160.0 - 212.117.175.255netname: SERVER-LUdescr: root eSolutionscountry: LUadmin-c: AB99-RIPEtech-c: RE655-RIPEstatus: ASSIGNED PAmnt-by: ROOT-MNTsource: RIPE # Filteredrole: root eSolutionsaddress: 35, rue John F. Kennedyaddress: 7327 Steinseladdress: Luxembourgphone: +352 20.500fax-no: +352 20.500.500e-mail: remarks:remarks: +------------------------------------+remarks: | Operational Issues: |remarks: | |remarks: +------------------------------------+remarks: | Abuse and Spam: |remarks: | |remarks: +------------------------------------+remarks:admin-c: RE655-RIPEtech-c: AB99-RIPEnic-hdl: RE655-RIPEmnt-by: ROOT-MNTsource: RIPE # Filteredperson: Andy BIERLAIRaddress: root SAaddress: 35, rue John F. Kennedyaddress: 7327 Steinseladdress: Luxembourgphone: +352 20.500fax-no: +352 20.500.500nic-hdl: AB99-RIPEmnt-by: ROOT-MNTremarks:remarks: +------------------------------------+remarks: | |remarks: | I did *NOT* spam your mailbox! |remarks: | I will *NOT* reply to abuse mails! |remarks: | |remarks: | Please contact ! |remarks: | |remarks: | Be friendly ... |remarks: | Unfriendly emails will be ignored! |remarks: | |remarks: +------------------------------------+remarks:e-mail: source: RIPE # Filteredroute: 212.117.160.0/19descr: root eSolutionsorigin: AS5577mnt-by: ROOT-MNTsource: RIPE # Filtered
domain: MSK.RUnserver: ns.ru.net.nserver: ns.spb.ru.nserver: ns1.relcom.ru.state: REGISTERED, DELEGATED, VERIFIEDorg: "Relcom.BN", Ltdphone: +7 499 1960820phone: +7 499 1960720phone: +7 499 196 0823fax-no: +7 499 1963295e-mail: registrar: RELCOM-REG-RIPNcreated: 1998.07.21paid-till: 2010.08.01source: TCI
This is almost certainly true. Very likely the same thing with atvclub.msk.ru, as well (although I can't be arsed even to check what kind of a content they host). It might not even be a client of theirs, it's entirely possible - perhaps even likely - that there's either a single infected system, or part of an actual botnet behind this.Judging by their site, root eSolutions seem most likely to be the negligent enabler rather than the culprit