April 2012 - anti-abuse-wg - mailman.ripe.net

OT: SPF deployment survey
by Alessandro Vesely 27 Apr '12

27 Apr '12

All, please excuse this slightly off-topic post. I know there are many mail operators here, and reviewing the SPF protocol /is/ related to anti-abuse, as SPF may help determining the recipients of abuse reports. The IETF working group that is going to write SPFBIS has nearly completed the evaluation of the current deployment. But, thus far, only the analysis of published SPF records was considered --not how SPF results are used. Please contribute to a better understanding by completing the following survey: https://www.surveymonkey.com/s/SPF-deployment-survey It will only take three minutes (ten questions on a single page). Please help reaching all mail admins by forwarding this prompt to specialized mailing lists and mail admins you are in touch with, worldwide. Thank you in advance!

1 0

Re: [anti-abuse-wg] 2011-06 Discussion Period extended until 7 May 2012 (Abuse Contact Management in the RIPE NCC Database)
by Leo Vegoda 26 Apr '12

26 Apr '12

Hi, Marco Schmidt wrote: [...] > Changes in version 2.0 include: > > - Overall rewording > - Description of the use of "abuse-c:" and "abuse-mailbox:" on differing > RIPE Database objects > - Removal of references to a transition period It is disappointing that this new proposal is still focused on a one-time process of adding additional contact information and does not address ongoing management of the published information. Until there is a policy requiring contact information to be regularly maintained, proposal 2011-06 is of limited value. Regards, Leo Vegoda

9 25

Re: [anti-abuse-wg] whats wrong in Kazakhstan ?
by Joe St Sauver 25 Apr '12

25 Apr '12

Frank commented: #We realized at lot of spam and other abuse coming from KZ networks #lately and found no email address nor abuse-mailbox-field in those #networks at all. Find their whois records below (its only the #networks we received abuse from during the last 4 days). Whenever I want to understand what's happening with a given country and spam, I often find the CBL to be terrifically helpful. For example, KZ is currently a top-ten botted country according to the CBL http://cbl.abuseat.org/country.html mentioning 172,239 entries Breaking that down by domain, http://cbl.abuseat.org/domain.html shows: -- 139,032 listings for online.kz -- 13,989 listings for nursat.net -- 9,686 listings for caravan.kz [there may be other kz domains that are also relevant, but at a level that's too low to show up on that by-domain summary] All three of the listed domains have domain whois with POC information for those who may want to reach out (I don't know if those doing so will need to speak Kazakh, or if Russian or English perhaps might be sufficient). Regards, Joe

1 0

abuse-contact is not going to fly unless we get all the legitimate players adopting it first
by Suresh Ramasubramanian 25 Apr '12

25 Apr '12

Like this for example - yes, not a formally defined abuse contact field, but they are so insistent that they should only receive spam reports at abuse(a)chello.pl Unfortunately - that address doesn't exist. If someone from Chello could please contact me about nigerians who keep abusing what is likely an open proxy at 89.70.30.128 I'd be obliged --srs (postmaster(a)lotuslive.com / AS27477 IBM Lotuslive) abuse(a)chello.pl SMTP error from remote mail server after RCPT TO:<abuse(a)chello.pl>: host smtp.upcpoczta.pl [213.46.255.2]: 550 5.1.1 <abuse(a)chello.pl> unknown recipient rejected route: 89.70.0.0/16 descr: UPC.pl origin: AS9141 remarks: Any abuse activities including, but not limited to spamming, remarks: hacking and intrusion attempts coming from chello.pl address remarks: space shall be reported ONLY to: remarks: remarks: abuse(a)chello.pl remarks: remarks: Any reports sent to any other e-mail addresses may be treated remarks: as SPAM itself and followed by legal actions remarks: against originator mnt-by: AS6830-MNT source: RIPE # Filtered -- Suresh Ramasubramanian (ops.lists(a)gmail.com)

7 15

whats wrong in Kazakhstan ?
by Frank Gadegast 25 Apr '12

25 Apr '12

Hi all, this might not be really related to this group, but maybe has an impact on a mandatory abuse field. We realized at lot of spam and other abuse coming from KZ networks lately and found no email address nor abuse-mailbox-field in those networks at all. Find their whois records below (its only the networks we received abuse from during the last 4 days). Is there any kind of law that prohibits publishing of emails in Kazakhstan ? Or is this only one big ISP with a lazy admin ? A weird coincident ? Is there anybody from Kazakhstan on this list, that can explain this situation ? Kind regards, Frank P.S.: we also checked most of these records with -B manually, still no email address -- MOTD: "have you enabled SSL on a website or mailbox today ?" -- PHADE Software - PowerWeb http://www.powerweb.de Inh. Dipl.-Inform. Frank Gadegast mailto:frank@powerweb.de Schinkelstrasse 17 fon: +49 33200 52920 14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921 ====================================================================== % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '176.222.130.0 - 176.222.131.255' inetnum: 176.222.130.0 - 176.222.131.255 netname: KZ-TNSPLUS-FTTB descr: FTTB_Taraz country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT remarks: INFRA-AW source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '176.222.130.0/23AS21299' route: 176.222.130.0/23 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '176.222.146.0 - 176.222.147.255' inetnum: 176.222.146.0 - 176.222.147.255 netname: KZ-TNSPLUS-FTTB descr: FTTB_Taraz country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT remarks: INFRA-AW source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '176.222.146.0/23AS21299' route: 176.222.146.0/23 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '176.222.148.0 - 176.222.151.255' inetnum: 176.222.148.0 - 176.222.151.255 netname: KZ-TNSPLUS-FTTB descr: FTTB_Almaty country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT remarks: INFRA-AW source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '176.222.148.0/22AS21299' route: 176.222.148.0/22 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '176.222.157.0 - 176.222.157.255' inetnum: 176.222.157.0 - 176.222.157.255 netname: KZ-TNSPLUS-FTTB descr: FTTB_Temirtau country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '176.222.157.0/24AS21299' route: 176.222.157.0/24 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '176.222.168.0 - 176.222.175.255' inetnum: 176.222.168.0 - 176.222.175.255 netname: KZ-TNSPLUS-FTTB descr: FTTB_Almaty country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT remarks: INFRA-AW source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '176.222.168.0/21AS21299' route: 176.222.168.0/21 descr: TNS Plus origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '176.222.188.0 - 176.222.189.255' inetnum: 176.222.188.0 - 176.222.189.255 netname: KZ-TNSPLUS-FTTB descr: FTTB_Semey country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '176.222.128.0/18AS21299' route: 176.222.128.0/18 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.88.224.0 - 178.88.239.255' inetnum: 178.88.224.0 - 178.88.239.255 netname: ALMATYTELECOM descr: JSC Kazakhtelecom, Almaty Affiliate country: KZ admin-c: OR708-RIPE tech-c: OR708-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Olga Reshetnyak address: JSC Kazakhtelecom, Almaty Affiliate address: Panfilov 74/72 str. 050004 address: Almaty address: Kazakhstan phone: +7 727 2736677 phone: +7 727 2710290 nic-hdl: OR708-RIPE source: RIPE # Filtered % Information related to '178.88.224.0/20AS9198' route: 178.88.224.0/20 descr: DIS origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.88.80.0 - 178.88.95.255' inetnum: 178.88.80.0 - 178.88.95.255 netname: ALMATYTELECOM descr: JSC Kazakhtelecom, Almaty Affiliate country: KZ admin-c: OR708-RIPE tech-c: OR708-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Olga Reshetnyak address: JSC Kazakhtelecom, Almaty Affiliate address: Panfilov 74/72 str. 050004 address: Almaty address: Kazakhstan phone: +7 727 2736677 phone: +7 727 2710290 nic-hdl: OR708-RIPE source: RIPE # Filtered % Information related to '178.88.80.0/21AS9198' route: 178.88.80.0/21 descr: DIS origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.89.136.0 - 178.89.143.255' inetnum: 178.89.136.0 - 178.89.143.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '178.89.136.0/21AS9198' route: 178.89.136.0/21 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.89.144.0 - 178.89.151.255' inetnum: 178.89.144.0 - 178.89.151.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '178.89.144.0/21AS9198' route: 178.89.144.0/21 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.89.144.0 - 178.89.151.255' inetnum: 178.89.144.0 - 178.89.151.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '178.89.144.0/21AS9198' route: 178.89.144.0/21 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.89.152.0 - 178.89.155.255' inetnum: 178.89.152.0 - 178.89.155.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '178.89.152.0/22AS9198' route: 178.89.152.0/22 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.89.152.0 - 178.89.155.255' inetnum: 178.89.152.0 - 178.89.155.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '178.89.152.0/22AS9198' route: 178.89.152.0/22 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.89.160.0 - 178.89.167.255' inetnum: 178.89.160.0 - 178.89.167.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '178.89.160.0/21AS9198' route: 178.89.160.0/21 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.89.168.0 - 178.89.175.255' inetnum: 178.89.168.0 - 178.89.175.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '178.89.168.0/21AS9198' route: 178.89.168.0/21 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.89.192.0 - 178.89.207.255' inetnum: 178.89.192.0 - 178.89.207.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '178.89.192.0/20AS9198' route: 178.89.192.0/20 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.91.31.0 - 178.91.31.31' inetnum: 178.91.31.0 - 178.91.31.31 netname: KAZRENA descr: in Shuchink country: KZ admin-c: SA2985-RIPE tech-c: SA2985-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Satekov Aibek address: Almaty, Satpaev street,22 address: KZ phone: +7 727 2926741 nic-hdl: SA2985-RIPE source: RIPE # Filtered % Information related to '178.91.0.0/19AS9198' route: 178.91.0.0/19 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '212.154.182.0 - 212.154.182.3' inetnum: 212.154.182.0 - 212.154.182.3 netname: Nomad_Insurance descr: Nomad Insurance descr: in Aktobe country: KZ admin-c: PS9080-RIPE tech-c: PS9080-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Prasolov Sergei address: Almaty, Timiryazev str, 15 address: KZ phone: +7 727 3212121 nic-hdl: PS9080-RIPE source: RIPE # Filtered % Information related to '212.154.180.0/22AS50482' route: 212.154.180.0/22 descr: Kazakhtelecom Data Network Administration origin: AS50482 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '212.154.236.0 - 212.154.236.3' inetnum: 212.154.236.0 - 212.154.236.3 netname: ALSI descr: TOO ALSI descr: in Kostanaiskaya obl, Borovskoe country: KZ admin-c: TR2652-RIPE tech-c: TR2652-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Tatyana Redkina address: Almaty, Dostyk, 91/1 address: KZ phone: +7 727 25030340 nic-hdl: TR2652-RIPE mnt-by: KNIC-MNT source: RIPE # Filtered % Information related to '212.154.236.0/22as50482' route: 212.154.236.0/22 descr: Kazakhtelecom Data Network Administration origin: as50482 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '2.132.0.0 - 2.132.15.255' inetnum: 2.132.0.0 - 2.132.15.255 netname: ALMATYTELECOM descr: JSC Kazakhtelecom, Almaty Affiliate country: KZ admin-c: OR708-RIPE tech-c: OR708-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Olga Reshetnyak address: JSC Kazakhtelecom, Almaty Affiliate address: Panfilov 74/72 str. 050004 address: Almaty address: Kazakhstan phone: +7 727 2736677 phone: +7 727 2710290 nic-hdl: OR708-RIPE source: RIPE # Filtered % Information related to '2.132.0.0/20AS9198' route: 2.132.0.0/20 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '2.132.128.0 - 2.132.143.255' inetnum: 2.132.128.0 - 2.132.143.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '2.132.128.0/20AS9198' route: 2.132.128.0/20 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '2.132.144.0 - 2.132.159.255' inetnum: 2.132.144.0 - 2.132.159.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '2.132.144.0/20AS9198' route: 2.132.144.0/20 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '2.132.16.0 - 2.132.31.255' inetnum: 2.132.16.0 - 2.132.31.255 netname: ALMATYTELECOM descr: JSC Kazakhtelecom, Almaty Affiliate country: KZ admin-c: OR708-RIPE tech-c: OR708-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Olga Reshetnyak address: JSC Kazakhtelecom, Almaty Affiliate address: Panfilov 74/72 str. 050004 address: Almaty address: Kazakhstan phone: +7 727 2736677 phone: +7 727 2710290 nic-hdl: OR708-RIPE source: RIPE # Filtered % Information related to '2.132.16.0/20AS9198' route: 2.132.16.0/20 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '37.99.1.0 - 37.99.1.255' inetnum: 37.99.1.0 - 37.99.1.255 netname: KZ-TNSPLUS-20120207 descr: FTTB_Uralsk country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '37.99.1.0/24AS21299' route: 37.99.1.0/24 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '37.99.112.0 - 37.99.115.255' inetnum: 37.99.112.0 - 37.99.115.255 netname: KZ-TNSPLUS-20120118 descr: FTTB_Kokshetau country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT remarks: INFRA-AW source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '37.99.112.0/22AS21299' route: 37.99.112.0/22 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '37.99.116.0 - 37.99.117.255' inetnum: 37.99.116.0 - 37.99.117.255 netname: KZ-TNSPLUS-20120118 descr: FTTB_Semey country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT remarks: INFRA-AW source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '37.99.116.0/23AS21299' route: 37.99.116.0/23 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '37.99.24.0 - 37.99.31.255' inetnum: 37.99.24.0 - 37.99.31.255 netname: KZ-TNSPLUS-20120118 descr: FTTB_Karaganda country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '37.99.24.0/21AS21299' route: 37.99.24.0/21 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '37.99.48.0 - 37.99.63.255' inetnum: 37.99.48.0 - 37.99.63.255 netname: KZ-TNSPLUS-20120118 descr: FTTB_Almaty country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '37.99.48.0/20AS21299' route: 37.99.48.0/20 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '37.99.80.0 - 37.99.87.255' inetnum: 37.99.80.0 - 37.99.87.255 netname: KZ-TNSPLUS-20120118 descr: FTTB_Almaty country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '37.99.80.0/21AS21299' route: 37.99.80.0/21 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '37.99.88.0 - 37.99.89.255' inetnum: 37.99.88.0 - 37.99.89.255 netname: KZ-TNSPLUS-20120118 descr: FTTB_Uralsk country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '37.99.88.0/23AS21299' route: 37.99.88.0/23 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '37.99.96.0 - 37.99.97.255' inetnum: 37.99.96.0 - 37.99.97.255 netname: KZ-TNSPLUS-20120118 descr: FTTB_Oskemen country: KZ admin-c: DG5853-RIPE tech-c: DG5853-RIPE status: ASSIGNED PA mnt-by: TNSPLUS-MNT source: RIPE # Filtered person: Dmitriy Gromov address: 38 Dostik str., Almaty, Kazakhstan phone: +7 705 833-55-55 nic-hdl: DG5853-RIPE mnt-by: TNSPLUS-MNT source: RIPE # Filtered % Information related to '37.99.96.0/23AS21299' route: 37.99.96.0/23 descr: 2DAY Telecom LLP origin: AS21299 mnt-by: TNSPLUS-MNT mnt-routes: SATELCOM-MNT mnt-routes: ORBITA-PLUS-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '82.200.137.0 - 82.200.137.31' inetnum: 82.200.137.0 - 82.200.137.31 netname: KTOWREALT descr: LLP K_TOWERS REALTY descr: in Almaty country: KZ admin-c: BR2515-RIPE tech-c: BR2515-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Boribaev Realty address: 050000 Almaty, Dostyk,180 phone: +7 727 23909050 nic-hdl: BR2515-RIPE mnt-by: KNIC-MNT source: RIPE # Filtered % Information related to '82.200.128.0/19AS9198' route: 82.200.128.0/19 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '82.200.224.0 - 82.200.224.127' inetnum: 82.200.224.0 - 82.200.224.127 netname: AKIMJ_POD descr: GU "Apparat akima Zhambylskoi obl" country: KZ admin-c: KW170-RIPE tech-c: KW170-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Kalashnikov Wladimir address: Taraz, st. Abaj, d.125 , Republic of Kazakhstan phone: +7 7262 454688 nic-hdl: KW170-RIPE source: RIPE # Filtered % Information related to '82.200.224.0/23AS9198' route: 82.200.224.0/23 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '88.204.136.0 - 88.204.136.31' inetnum: 88.204.136.0 - 88.204.136.31 netname: KABLAN descr: KABLAN LLP descr: Almaty, str ABAI 26 a country: KZ admin-c: AG6698-RIPE tech-c: AG6698-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: ACHMEDIAROVA GULNARA address: Almaty, str ABAI 26 a address: KZ phone: +7 3272 599392 nic-hdl: AG6698-RIPE source: RIPE # Filtered % Information related to '88.204.128.0/20AS9198' route: 88.204.128.0/20 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '88.204.158.0 - 88.204.158.63' inetnum: 88.204.158.0 - 88.204.158.63 netname: O2DISIGN descr: o2Design country: KZ admin-c: KO566-RIPE tech-c: KO566-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Kopanica Olga address: microdistrict ¹ 6, 25 office 14 address: Almaty phone: +7 3272 508383 nic-hdl: KO566-RIPE source: RIPE # Filtered % Information related to '88.204.128.0/19AS9198' route: 88.204.128.0/19 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '88.204.170.0 - 88.204.170.3' inetnum: 88.204.170.0 - 88.204.170.3 netname: IPPERCENTRE descr: Kalymkulov Elnar Alievitch ip. country: KZ admin-c: EK1920-RIPE tech-c: EK1920-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Elnar Kalymkulov address: 473000 Astana, Manas st.36 phone: +7 7172 527971 nic-hdl: EK1920-RIPE source: RIPE # Filtered % Information related to '88.204.168.0/21AS9198' route: 88.204.168.0/21 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '89.218.122.0 - 89.218.122.3' inetnum: 89.218.122.0 - 89.218.122.3 netname: KEREMET descr: KEREMET SAUDA LTD country: KZ admin-c: KA3141-RIPE tech-c: KA3141-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: KIMBAEV ALMAS address: Chimbay Str. 107 address: city KyzylOrda phone: +7 72422 224086 nic-hdl: KA3141-RIPE mnt-by: KNIC-MNT source: RIPE # Filtered % Information related to '89.218.120.0/22AS9198' route: 89.218.120.0/22 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '89.218.212.0 - 89.218.212.3' inetnum: 89.218.212.0 - 89.218.212.3 netname: ARMAN descr: ARMAN descr: in Aktau, Building 39B, microdistrict 8 country: KZ admin-c: IN426-RIPE tech-c: IN426-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Ibrashev Nurlan address: Aktau, Building 39B, microdistrict 8 address: KZ phone: +7 7292 300366 phone: +7 701 5319663 nic-hdl: IN426-RIPE source: RIPE # Filtered % Information related to '89.218.208.0/21AS9198' route: 89.218.208.0/21 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '89.218.255.0 - 89.218.255.3' inetnum: 89.218.255.0 - 89.218.255.3 netname: ALMA_ODT descr: JSC Kazakhtelecom, Almaty Affiliate descr: For the service purposes, for joining the equipment country: KZ admin-c: EY229-RIPE tech-c: EY229-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Erasilov Yalihan address: 39A, Shaikovskogo., Almaty, Republic of Kazakhstan address: KZ phone: +7 728 2 21 16 21 nic-hdl: EY229-RIPE mnt-by: KNIC-MNT source: RIPE # Filtered % Information related to '89.218.248.0/21AS9198' route: 89.218.248.0/21 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '89.218.38.0 - 89.218.38.7' inetnum: 89.218.38.0 - 89.218.38.7 netname: ALLER descr: LTD Shaller Kazahstan descr: in Almaty country: KZ admin-c: LO1217-RIPE tech-c: LO1217-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Lyadmila Ostankina address: : 050043 Almaty, Samal-2.77 phone: +7 727 22642663 nic-hdl: LO1217-RIPE mnt-by: KNIC-MNT source: RIPE # Filtered % Information related to '89.218.32.0/20AS9198' route: 89.218.32.0/20 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '89.218.39.0 - 89.218.39.63' inetnum: 89.218.39.0 - 89.218.39.63 netname: KAZINTERCOM descr: LTD KAZINTERCOM descr: in Almaty country: KZ admin-c: PV4983-RIPE tech-c: PV4983-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Ponamorev Vitaliy address: 050043 Almaty, Manas str.,50/V phone: +7 727 2576689 nic-hdl: PV4983-RIPE mnt-by: KNIC-MNT source: RIPE # Filtered % Information related to '89.218.39.0/24AS9198' route: 89.218.39.0/24 descr: Kazakhtelecom Megaline Almaty Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '89.218.50.0 - 89.218.50.3' inetnum: 89.218.50.0 - 89.218.50.3 netname: NCAGIP descr: Nauchnyi centr akusherstva,gynecologii i perinatologii descr: in Almaty country: KZ admin-c: BA3892-RIPE tech-c: BA3892-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Belych Artem address: 050000Almaty, Dostik 125 address: KZ phone: +7 727 3004566 nic-hdl: BA3892-RIPE mnt-by: KNIC-MNT source: RIPE # Filtered % Information related to '89.218.48.0/21AS9198' route: 89.218.48.0/21 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '89.218.52.0 - 89.218.52.15' inetnum: 89.218.52.0 - 89.218.52.15 netname: KOMTEL descr: " KOMTEL" LLC descr: Almaty country: KZ admin-c: DV1669-RIPE tech-c: DV1669-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Doncov Vadim address: 4, Tinibaeva st., Shymkent, Republic of Kazakhstan phone: +7 701 7269544 nic-hdl: DV1669-RIPE source: RIPE # Filtered % Information related to '89.218.48.0/21AS9198' route: 89.218.48.0/21 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '89.218.61.0 - 89.218.61.3' inetnum: 89.218.61.0 - 89.218.61.3 netname: SOFDC descr: LLP SOFTDECO descr: in Almaty country: KZ admin-c: MO4341-RIPE tech-c: MO4341-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Mamarkova Olga address: Almaty, Abaya, 153.of 33 address: KZ phone: +7 727 2952515 nic-hdl: MO4341-RIPE mnt-by: KNIC-MNT source: RIPE # Filtered % Information related to '89.218.61.0/24AS9198' route: 89.218.61.0/24 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '89.218.94.0 - 89.218.94.3' inetnum: 89.218.94.0 - 89.218.94.3 netname: SALONSVYAZISULPAK descr: Salon svyasi Sulpak ltd descr: Astana mkr.2A dom.3 country: KZ admin-c: TE868-RIPE tech-c: TE868-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Talgarov Erzhan address: 473000 Astana, mkr.2A dom.3 phone: +7 3172 341009 nic-hdl: TE868-RIPE source: RIPE # Filtered % Information related to '89.218.64.0/19AS9198' route: 89.218.64.0/19 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '89.218.95.0 - 89.218.95.7' inetnum: 89.218.95.0 - 89.218.95.7 netname: ASTANATELECOM_GCT descr: JSC Kazakhtelecom, Astana Affiliate descr: For the removed access descr: Astana country: KZ remarks: INFRA-AW admin-c: GK1323-RIPE tech-c: GK1323-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Gulhan Karmanova address: 473000 Astana, Abaya 78 phone: +7 3172 330403 nic-hdl: GK1323-RIPE source: RIPE # Filtered % Information related to '89.218.64.0/19AS9198' route: 89.218.64.0/19 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.10.0 - 92.46.11.255' inetnum: 92.46.10.0 - 92.46.11.255 netname: ALMATYTELECOM descr: JSC Kazakhtelecom, Almaty Affiliate country: KZ admin-c: OR708-RIPE tech-c: OR708-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Olga Reshetnyak address: JSC Kazakhtelecom, Almaty Affiliate address: Panfilov 74/72 str. 050004 address: Almaty address: Kazakhstan phone: +7 727 2736677 phone: +7 727 2710290 nic-hdl: OR708-RIPE source: RIPE # Filtered % Information related to '92.46.10.0/23AS9198' route: 92.46.10.0/23 descr: Megaline Almaty origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.126.0 - 92.46.126.31' inetnum: 92.46.126.0 - 92.46.126.31 netname: TOOELITCOM descr: TOOELITCOM country: KZ admin-c: AS4033-RIPE tech-c: AS4033-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Ainabekova Sayle address: Astana, Potanina st. 3 phone: +7 7172 177247 nic-hdl: AS4033-RIPE source: RIPE # Filtered % Information related to '92.46.64.0/18AS9198' route: 92.46.64.0/18 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.128.0 - 92.46.129.255' inetnum: 92.46.128.0 - 92.46.129.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '92.46.128.0/19AS9198' route: 92.46.128.0/19 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.132.0 - 92.46.133.255' inetnum: 92.46.132.0 - 92.46.133.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '92.46.133.0/24AS9198' route: 92.46.133.0/24 descr: Kazakhtelecom Megaline Karaganda Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.134.0 - 92.46.135.255' inetnum: 92.46.134.0 - 92.46.135.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '92.46.134.0/24AS9198' route: 92.46.134.0/24 descr: Kazakhtelecom Megaline Karaganda Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.136.0 - 92.46.137.255' inetnum: 92.46.136.0 - 92.46.137.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '92.46.136.0/24AS9198' route: 92.46.136.0/24 descr: Kazakhtelecom Megaline Karaganda Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.144.0 - 92.46.153.255' inetnum: 92.46.144.0 - 92.46.153.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '92.46.148.0/24AS9198' route: 92.46.148.0/24 descr: Kazakhtelecom Megaline Karaganda Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.14.0 - 92.46.15.255' inetnum: 92.46.14.0 - 92.46.15.255 netname: ALMATYTELECOM descr: JSC Kazakhtelecom, Almaty Affiliate country: KZ admin-c: OR708-RIPE tech-c: OR708-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Olga Reshetnyak address: JSC Kazakhtelecom, Almaty Affiliate address: Panfilov 74/72 str. 050004 address: Almaty address: Kazakhstan phone: +7 727 2736677 phone: +7 727 2710290 nic-hdl: OR708-RIPE source: RIPE # Filtered % Information related to '92.46.14.0/23AS9198' route: 92.46.14.0/23 descr: Kazakhtelecom Megaline Almaty Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.154.0 - 92.46.161.255' inetnum: 92.46.154.0 - 92.46.161.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '92.46.156.0/22AS9198' route: 92.46.156.0/22 descr: Kazakhtelecom Megaline Karaganda Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.162.0 - 92.46.173.255' inetnum: 92.46.162.0 - 92.46.173.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '92.46.164.0/22AS9198' route: 92.46.164.0/22 descr: Kazakhtelecom Megaline Karaganda Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.20.0 - 92.46.21.255' inetnum: 92.46.20.0 - 92.46.21.255 netname: ALMATYTELECOM descr: JSC Kazakhtelecom, Almaty Affiliate country: KZ admin-c: OR708-RIPE tech-c: OR708-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Olga Reshetnyak address: JSC Kazakhtelecom, Almaty Affiliate address: Panfilov 74/72 str. 050004 address: Almaty address: Kazakhstan phone: +7 727 2736677 phone: +7 727 2710290 nic-hdl: OR708-RIPE source: RIPE # Filtered % Information related to '92.46.20.0/23AS9198' route: 92.46.20.0/23 descr: Kazakhtelecom Megaline Almaty Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.22.0 - 92.46.23.255' inetnum: 92.46.22.0 - 92.46.23.255 netname: ALMATYTELECOM descr: JSC Kazakhtelecom, Almaty Affiliate country: KZ admin-c: OR708-RIPE tech-c: OR708-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Olga Reshetnyak address: JSC Kazakhtelecom, Almaty Affiliate address: Panfilov 74/72 str. 050004 address: Almaty address: Kazakhstan phone: +7 727 2736677 phone: +7 727 2710290 nic-hdl: OR708-RIPE source: RIPE # Filtered % Information related to '92.46.22.0/23AS9198' route: 92.46.22.0/23 descr: Kazakhtelecom Megaline Almaty Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.26.0 - 92.46.30.255' inetnum: 92.46.26.0 - 92.46.30.255 netname: ALMATYTELECOM descr: JSC Kazakhtelecom, Almaty Affiliate country: KZ admin-c: OR708-RIPE tech-c: OR708-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Olga Reshetnyak address: JSC Kazakhtelecom, Almaty Affiliate address: Panfilov 74/72 str. 050004 address: Almaty address: Kazakhstan phone: +7 727 2736677 phone: +7 727 2710290 nic-hdl: OR708-RIPE source: RIPE # Filtered % Information related to '92.46.26.0/24AS9198' route: 92.46.26.0/24 descr: Kazakhtelecom Megaline Almaty Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.35.0 - 92.46.35.31' inetnum: 92.46.35.0 - 92.46.35.31 netname: SAGIMBEKOVA descr: SAGIMBEKOVA descr: in Almaty country: KZ admin-c: SN2324-RIPE tech-c: SN2324-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: SAGIMBEKOVA NURBIBA address: 050000 Almaty, Kiz Gibek str 2/176 phone: +7 7272 2558989 nic-hdl: SN2324-RIPE source: RIPE # Filtered % Information related to '92.46.0.0/18AS9198' route: 92.46.0.0/18 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.49.0 - 92.46.49.3' inetnum: 92.46.49.0 - 92.46.49.3 netname: Bairashew descr: in Almaty country: KZ admin-c: BA2916-RIPE tech-c: BA2916-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Bairashew Akibek address: 050000 Almaty, Zetisu 2-37-16 phone: +7 7272 2566768 nic-hdl: BA2916-RIPE source: RIPE # Filtered % Information related to '92.46.0.0/18AS9198' route: 92.46.0.0/18 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.51.0 - 92.46.51.15' inetnum: 92.46.51.0 - 92.46.51.15 netname: ENOTROC descr: LLP T-ONE CORPORATION descr: 1 Novay astr., Amlatinskaya oblast descr: in Almaty country: KZ admin-c: IV1069-RIPE tech-c: IV1069-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Ivaschenko Vitaliy address: Almaty, Al-Farabi, 93 address: KZ phone: +7 727 3905063 nic-hdl: IV1069-RIPE mnt-by: KNIC-MNT source: RIPE # Filtered % Information related to '92.46.0.0/18AS9198' route: 92.46.0.0/18 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.58.0 - 92.46.58.7' inetnum: 92.46.58.0 - 92.46.58.7 netname: BETUKAZ descr: "Kaz-Turk Beton", Almaty country: KZ admin-c: SA2276-RIPE tech-c: SA2276-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Shurabaeva Asel address: Burundaiskaya, 93ZH address: Almaty phone: +7 7272 346171 fax-no: +7 7272 346171 nic-hdl: SA2276-RIPE source: RIPE # Filtered % Information related to '92.46.0.0/18AS9198' route: 92.46.0.0/18 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.6.0 - 92.46.7.255' inetnum: 92.46.6.0 - 92.46.7.255 netname: ALMATYTELECOM descr: JSC Kazakhtelecom, Almaty Affiliate country: KZ remarks: INFRA-AW admin-c: OR708-RIPE tech-c: OR708-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Olga Reshetnyak address: JSC Kazakhtelecom, Almaty Affiliate address: Panfilov 74/72 str. 050004 address: Almaty address: Kazakhstan phone: +7 727 2736677 phone: +7 727 2710290 nic-hdl: OR708-RIPE source: RIPE # Filtered % Information related to '92.46.6.0/23AS9198' route: 92.46.6.0/23 descr: Kazakhtelecom Megaline Almaty Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.46.8.0 - 92.46.9.255' inetnum: 92.46.8.0 - 92.46.9.255 netname: ALMATYTELECOM descr: JSC Kazakhtelecom, Almaty Affiliate country: KZ admin-c: OR708-RIPE tech-c: OR708-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Olga Reshetnyak address: JSC Kazakhtelecom, Almaty Affiliate address: Panfilov 74/72 str. 050004 address: Almaty address: Kazakhstan phone: +7 727 2736677 phone: +7 727 2710290 nic-hdl: OR708-RIPE source: RIPE # Filtered % Information related to '92.46.8.0/23AS9198' route: 92.46.8.0/23 descr: Kazakhtelecom Megaline Almaty Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.47.110.0 - 92.47.110.3' inetnum: 92.47.110.0 - 92.47.110.3 netname: Bostan descr: TOO "Bostan", Taraz country: KZ admin-c: TLY1-RIPE tech-c: TLY1-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Tolochkova Lidija Yakovlevna address: Zhambylskaja obl, g. Taraz, ul. Kazybek bi 142 a, Republic of Kazakhstan phone: +7 7262 457525 nic-hdl: TLY1-RIPE source: RIPE # Filtered % Information related to '92.47.96.0/20AS9198' route: 92.47.96.0/20 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.47.163.0 - 92.47.163.63' inetnum: 92.47.163.0 - 92.47.163.63 netname: Business_Telecom descr: Business Telecom LLP descr: in Almaty, Bogenbay. str. 150 country: KZ admin-c: AS349-RIPE tech-c: AS349-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Azamat Syzdykov address: Almaty, Bogenbay. str. 150 address: KZ phone: +7 727 3150050 fax-no: +7 727 3150050 nic-hdl: AS349-RIPE source: RIPE # Filtered % Information related to '92.46.0.0/15AS9198' route: 92.46.0.0/15 descr: Kazakhtelecom origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.47.164.0 - 92.47.171.255' inetnum: 92.47.164.0 - 92.47.171.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '92.47.164.0/22AS9198' route: 92.47.164.0/22 descr: Kazakhtelecom Megaline Karaganda Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.47.64.0 - 92.47.65.255' inetnum: 92.47.64.0 - 92.47.65.255 netname: AKTAMETRO descr: JSC Kazakhtelecom, Aktau Affiliate descr: Metro Ethernet Network country: KZ remarks: INFRA-AW admin-c: MA8421-RIPE tech-c: MA8421-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Murat Aitmagametov address: JSC Kazakhtelecom, Mangystau Affiliate address: 14 microdistrict, Dom svyazi address: Aktau, 130000 address: Kazakhstan phone: +7 7292 316705 phone: +7 701 7603523 nic-hdl: MA8421-RIPE source: RIPE # Filtered % Information related to '92.47.64.0/24AS9198' route: 92.47.64.0/24 descr: Kazakhtelecom Megaline Aktau Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '92.47.69.0 - 92.47.71.255' inetnum: 92.47.69.0 - 92.47.71.255 netname: AKTAMETRO descr: JSC Kazakhtelecom, Aktau Affiliate descr: Metro Ethernet Network country: KZ remarks: INFRA-AW admin-c: MA8421-RIPE tech-c: MA8421-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Murat Aitmagametov address: JSC Kazakhtelecom, Mangystau Affiliate address: 14 microdistrict, Dom svyazi address: Aktau, 130000 address: Kazakhstan phone: +7 7292 316705 phone: +7 701 7603523 nic-hdl: MA8421-RIPE source: RIPE # Filtered % Information related to '92.47.71.0/24AS9198' route: 92.47.71.0/24 descr: Kazakhtelecom Megaline Aktau Network origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.56.245.0 - 95.56.245.255' inetnum: 95.56.245.0 - 95.56.245.255 netname: FTI descr: INSTITUTE OF PHYSICS AND TECHNOLOGY LLC descr: in Almaty country: KZ admin-c: NV4722-RIPE tech-c: NV4722-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Nazarenko Vladimir address: 050014 Almaty, Ibragimova,11 phone: +7 7273 865513 nic-hdl: NV4722-RIPE source: RIPE # Filtered % Information related to '95.56.245.0/24AS9198' route: 95.56.245.0/24 descr: Megaline Almaty origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.0.0 - 95.57.7.255' inetnum: 95.57.0.0 - 95.57.7.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ remarks: INFRA-AW admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.0.0/21AS9198' route: 95.57.0.0/21 descr: Megaline Karaganda origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.10.0 - 95.57.25.255' inetnum: 95.57.10.0 - 95.57.25.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.10.0/23AS9198' route: 95.57.10.0/23 descr: Megaline Karaganda origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.107.0 - 95.57.107.255' inetnum: 95.57.107.0 - 95.57.107.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.107.0/24AS9198' route: 95.57.107.0/24 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.108.0 - 95.57.111.255' inetnum: 95.57.108.0 - 95.57.111.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.108.0/22AS9198' route: 95.57.108.0/22 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS1) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.108.0 - 95.57.111.255' inetnum: 95.57.108.0 - 95.57.111.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.108.0/22AS9198' route: 95.57.108.0/22 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.112.0 - 95.57.115.255' inetnum: 95.57.112.0 - 95.57.115.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.112.0/22AS9198' route: 95.57.112.0/22 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.116.0 - 95.57.117.255' inetnum: 95.57.116.0 - 95.57.117.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.116.0/23AS9198' route: 95.57.116.0/23 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.216.0 - 95.57.216.3' inetnum: 95.57.216.0 - 95.57.216.3 netname: AELITA descr: AELITA descr: in Aktobe country: KZ admin-c: KN1063-RIPE tech-c: KN1063-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Kuchugura Nadezhda address: 030000, Aktobe, Gaziza Zhubanovs st, 46 phone: +7 7132 514599 nic-hdl: KN1063-RIPE source: RIPE # Filtered % Information related to '95.57.192.0/19AS9198' route: 95.57.192.0/19 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.26.0 - 95.57.41.255' inetnum: 95.57.26.0 - 95.57.41.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.28.0/22AS9198' route: 95.57.28.0/22 descr: Megaline Karaganda origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.0.0 - 95.57.7.255' inetnum: 95.57.0.0 - 95.57.7.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ remarks: INFRA-AW admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.0.0/21AS9198' route: 95.57.0.0/21 descr: Megaline Karaganda origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.0.0 - 95.57.7.255' inetnum: 95.57.0.0 - 95.57.7.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ remarks: INFRA-AW admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.0.0/21AS9198' route: 95.57.0.0/21 descr: Megaline Karaganda origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.59.0 - 95.57.74.255' inetnum: 95.57.59.0 - 95.57.74.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.60.0/22AS9198' route: 95.57.60.0/22 descr: Megaline Karaganda origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.75.0 - 95.57.82.255' inetnum: 95.57.75.0 - 95.57.82.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.76.0/22AS9198' route: 95.57.76.0/22 descr: Megaline Karaganda origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.57.91.0 - 95.57.106.255' inetnum: 95.57.91.0 - 95.57.106.255 netname: KRGMETRO descr: JSC Kazakhtelecom, Karaganda Affiliate descr: Metro Ethernet Network country: KZ admin-c: SF3380-RIPE tech-c: SF3380-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Sergey Fainitskiy address: JSC Kazakhtelecom, Karaganda Affiliate address: 31 Ermekova Str., Karaganda, 100000 address: Kazakhstan phone: +7 7212 433916 nic-hdl: SF3380-RIPE source: RIPE # Filtered % Information related to '95.57.92.0/23AS9198' route: 95.57.92.0/23 descr: Megaline Karaganda origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.58.190.0 - 95.58.191.255' inetnum: 95.58.190.0 - 95.58.191.255 netname: EKZ_ODT descr: JSC Kazakhtelecom, East Kazakhstan Affiliate descr: Dynamic dial-up pool descr: Ust-Kamenogorsk country: KZ remarks: INFRA-AW admin-c: KVY19-RIPE tech-c: KVY19-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Kubyshkin Vitaliy Yuryevich address: 67, str. Kazakhstan, Ust-Kamenogorsk phone: +7 7232 267345 nic-hdl: KVY19-RIPE source: RIPE # Filtered % Information related to '95.58.191.0/24AS9198' route: 95.58.191.0/24 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.58.28.0 - 95.58.28.3' inetnum: 95.58.28.0 - 95.58.28.3 netname: UNISCREDIT descr: UNISCREDIT in Almaty country: KZ admin-c: BD2309-RIPE tech-c: BD2309-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Burkitbaev Daniyar address: Almaty, Rozybakiev str, home 70 Kazakhstan phone: +7 727 3794584 fax-no: +7 727 3794632 nic-hdl: BD2309-RIPE source: RIPE # Filtered % Information related to '95.58.28.0/24AS9198' route: 95.58.28.0/24 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS4) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.58.40.0 - 95.58.41.255' inetnum: 95.58.40.0 - 95.58.41.255 netname: AKTAMETRO descr: JSC Kazakhtelecom, Mangystau Affiliate descr: Metro Ethernet Network country: KZ admin-c: MA8421-RIPE tech-c: MA8421-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Murat Aitmagametov address: JSC Kazakhtelecom, Mangystau Affiliate address: 14 microdistrict, Dom svyazi address: Aktau, 130000 address: Kazakhstan phone: +7 7292 316705 phone: +7 701 7603523 nic-hdl: MA8421-RIPE source: RIPE # Filtered % Information related to '95.58.40.0/23AS9198' route: 95.58.40.0/23 descr: Megaline Aktau origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.58.42.0 - 95.58.49.255' inetnum: 95.58.42.0 - 95.58.49.255 netname: AKTAMETRO descr: JSC Kazakhtelecom, Mangystau Affiliate descr: Metro Ethernet Network country: KZ admin-c: MA8421-RIPE tech-c: MA8421-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Murat Aitmagametov address: JSC Kazakhtelecom, Mangystau Affiliate address: 14 microdistrict, Dom svyazi address: Aktau, 130000 address: Kazakhstan phone: +7 7292 316705 phone: +7 701 7603523 nic-hdl: MA8421-RIPE source: RIPE # Filtered % Information related to '95.58.42.0/23AS9198' route: 95.58.42.0/23 descr: Megaline Aktau origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.58.50.0 - 95.58.50.255' inetnum: 95.58.50.0 - 95.58.50.255 netname: AKTAMETRO descr: JSC Kazakhtelecom, Mangystau Affiliate descr: Metro Ethernet Network country: KZ admin-c: MA8421-RIPE tech-c: MA8421-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Murat Aitmagametov address: JSC Kazakhtelecom, Mangystau Affiliate address: 14 microdistrict, Dom svyazi address: Aktau, 130000 address: Kazakhstan phone: +7 7292 316705 phone: +7 701 7603523 nic-hdl: MA8421-RIPE source: RIPE # Filtered % Information related to '95.58.50.0/24AS9198' route: 95.58.50.0/24 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.58.51.0 - 95.58.54.255' inetnum: 95.58.51.0 - 95.58.54.255 netname: AKTAMETRO descr: JSC Kazakhtelecom, Mangystau Affiliate descr: Metro Ethernet Network country: KZ admin-c: MA8421-RIPE tech-c: MA8421-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Murat Aitmagametov address: JSC Kazakhtelecom, Mangystau Affiliate address: 14 microdistrict, Dom svyazi address: Aktau, 130000 address: Kazakhstan phone: +7 7292 316705 phone: +7 701 7603523 nic-hdl: MA8421-RIPE source: RIPE # Filtered % Information related to '95.58.54.0/24AS9198' route: 95.58.54.0/24 descr: Megaline Ustkamenogorsk origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS2) % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '95.58.57.0 - 95.58.62.255' inetnum: 95.58.57.0 - 95.58.62.255 netname: AKTAMETRO descr: JSC Kazakhtelecom, Mangystau Affiliate descr: Metro Ethernet Network country: KZ admin-c: MA8421-RIPE tech-c: MA8421-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT source: RIPE # Filtered person: Murat Aitmagametov address: JSC Kazakhtelecom, Mangystau Affiliate address: 14 microdistrict, Dom svyazi address: Aktau, 130000 address: Kazakhstan phone: +7 7292 316705 phone: +7 701 7603523 nic-hdl: MA8421-RIPE source: RIPE # Filtered % Information related to '95.58.57.0/24AS9198' route: 95.58.57.0/24 descr: Megaline Aktau origin: AS9198 mnt-by: KNIC-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.6.12 (WHOIS3)

2 1

Re: [anti-abuse-wg] 2011-06 Discussion Period extended until 7 May 2012 (Abuse Contact Management in the RIPE NCC Database)
by chrish＠consol.net 22 Apr '12

22 Apr '12

hi! On 04/16/2012 03:24 PM, Marco Schmidt wrote: > We encourage you to review this RIPE Policy Proposal and send your > comments to <anti-abuse-wg(a)ripe.net> by 7 May 2012. -1, unchanged. it's essentially unchanged, so the reasons as discussed on this ml are unchanged (doesn't simplify, doesn't help, just complicates, with foreseeable consecutive problems - it's a step backwards). regards, Chris

7 13

Lack of contact from ORG-LA16-RIPE regarding spam / 46.109.195.227
by Chris 21 Apr '12

21 Apr '12

46.109.195.227 is a well known, abusive IP address that is likely an open proxy used to send out spam messages on Wordpress. I have contacted abuse(a)lattelecom.lv numerous times and this IP address continues to be abusive. Nameservers for the domain are from Hostkey - RIPE-ERX-141 / AS49335 Domain is xrumerservice.org, which should not be difficult to find online. Anyone care to instruct me how RIPE handles abuse differently than ARIN because this guy is getting pretty annoying when I have 50+ blogs getting 5 messages each from him and if you think Akismet / anti spam plugins are the solution, it has made the problem this much worse and encourages "fast flux" use of IP address, such as with cloud hosting services, to temporarily abuse an IP address and dump it before it gets traditionally blacklisted. -- --C "The dumber people think you are, the more surprised they're going to be when you kill them." - Sir William Clayton

4 4

Re: [anti-abuse-wg] anti-abuse-wg Digest, Vol 8, Issue 19
by Karl-Josef Ziegler 17 Apr '12

17 Apr '12

Hello! > The different pieces of contact information are all potential ways to > get in touch with the Internet number resource holder. If you have > difficulties reaching them via any of those details, you can report this > to us. I would recommend making a reasonable attempt to contact them > first though, for example by giving them a phone call if you find that > their email addresses are no longer working. My experience: I've used the form because the email contacts from a provider in Romania were invalid. The phone contact given in the RIPE database was only a mobile phone number in Romania. I searched for this number in the web and only get a few results which all directed to the entry in the RIPE database. So it seems that this (prepaid?) phone was only used to register this IP space with RIPE. My claim was denied because I didn't made an attempt to contact the provider on mobile phone in Romania. I didn't contact them because I don't speak Romanian and I feared retaliation from possible criminals in Romania. So for an individual it may be very difficult to fulfill all the external requirements which are made by RIPE NCC. And, of course, RIPE may be in a better position to repel retaliations. RIPE NCC wrote back that they don't have the staff to check if the entries in the database are correct. So if RIPE will guarantee the validity of the database today they seem not to have the personal capacity for research. Best regards, - Karl-Josef Ziegler

5 9

Re: [anti-abuse-wg] 2011-06 Discussion Period extended until 7 May 2012 (Abuse Contact Management in the RIPE NCC Database)
by Gilles Massen 17 Apr '12

17 Apr '12

Hello, > Changes in version 2.0 include: > > - Overall rewording > - Description of the use of "abuse-c:" and "abuse-mailbox:" on differing > RIPE Database objects > - Removal of references to a transition period What I still miss is a clear positioning of the IRT object vs. abuse-c. While these may not overlap completely, they certainly would to a large extend for a lot of CERTs, thus creating redundant data. So I'd join Leo on his comments that the use of the object should be clearer before creating it. If not the worst case might be that we end up with another randomly used object. Best, Gilles -- Fondation RESTENA - DNS-LU 6, rue Coudenhove-Kalergi L-1359 Luxembourg tel: (+352) 424409 fax: (+352) 422473

1 0

Re: [anti-abuse-wg] 2011-06 Discussion Period extended until 7 May 2012 (Abuse Contact Management in the RIPE NCC Database)
by Frank Gadegast 16 Apr '12

16 Apr '12

Marco Schmidt wrote: > Dear colleagues, Hello, I like to recommend the following change, from "The "abuse-mailbox:" attribute must be available in an unrestricted way via whois, APIs and future techniques." to "The "abuse-mailbox:" attribute for a given object must be available in an unrestricted way via whois, APIs and future techniques with a single request". because its not clear how the right abuse-mailbox field could be found for example via whois. It will be no help, if there is a first request needed to find the abuse-c and a second request to read the abuse-mailbox field. This could lead to reach limits, if either the access to the abuse-c field is limited or if there is no other method (like a new whois flag) to directly request the abuse-mailbox field from the abuse-c Somebody at the RIPE NCC told me last week, that they intend to integrate the abuse-finder-tool (wich will surely return the abuse-mailbox-field from the abuse-c in a preferred manner) into whois with a new option, if the proposal gets through, but it should be clearer in the proposal, that its intention is, to receive the value of the abuse-mailbox field with simply one request. Kind regards, Frank > > The text of RIPE Policy Proposal 2011-06, "Abuse Contact Management in > the RIPE NCC Database", has been revised based on community feedback > received on the mailing list. > > We published the new version (version 2.0) today, 16 April. As a result, > a new Discussion Phase is set for the proposal. > > Changes in version 2.0 include: > > - Overall rewording > - Description of the use of "abuse-c:" and "abuse-mailbox:" on differing > RIPE Database objects > - Removal of references to a transition period > > You can find the full proposal at: > https://www.ripe.net/ripe/policies/proposals/2011-06 > > We encourage you to review this RIPE Policy Proposal and send your > comments to<anti-abuse-wg(a)ripe.net> by 7 May 2012. > > Regards > > Marco Schmidt > on behalf of the Policy Development Office > RIPE NCC > > > > -- Mit freundlichen Gruessen, -- MOTD: "have you enabled SSL on a website or mailbox today ?" -- PHADE Software - PowerWeb http://www.powerweb.de Inh. Dipl.-Inform. Frank Gadegast mailto:frank@powerweb.de Schinkelstrasse 17 fon: +49 33200 52920 14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921 ======================================================================

1 0

2011-06 Discussion Period extended until 7 May 2012 (Abuse Contact Management in the RIPE NCC Database)
by Marco Schmidt 16 Apr '12

16 Apr '12

Dear colleagues, The text of RIPE Policy Proposal 2011-06, "Abuse Contact Management in the RIPE NCC Database", has been revised based on community feedback received on the mailing list. We published the new version (version 2.0) today, 16 April. As a result, a new Discussion Phase is set for the proposal. Changes in version 2.0 include: - Overall rewording - Description of the use of "abuse-c:" and "abuse-mailbox:" on differing RIPE Database objects - Removal of references to a transition period You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2011-06 We encourage you to review this RIPE Policy Proposal and send your comments to <anti-abuse-wg(a)ripe.net> by 7 May 2012. Regards Marco Schmidt on behalf of the Policy Development Office RIPE NCC

1 0

Re: [anti-abuse-wg] abuse email address validation - VOTE
by Jørgen Hovland 14 Apr '12

14 Apr '12

1 0

Introducing the RIPE NCC Report Form
by Laura Cobley 14 Apr '12

14 Apr '12

[Apologies for duplicate emails] Dear colleagues, We would like to introduce the RIPE NCC Report Form. Using this form, you can now easily report various issues, including abnormalities in Internet number resource registrations, to us for further investigation. By making it easy to report these issues to us and by putting a clear process in place, we aim to work together with you to further improve the quality of the data in the Internet number resource registry. The first release of the form offers basic functionality. We will review the form, its usage and your feedback before deciding whether further development is needed in the future. You can find more details at: https://labs.ripe.net/Members/andrea/ripe-ncc-report-form If you have any questions or feedback, please contact <ncc(a)ripe.net>. Best regards, Laura Cobley RIPE NCC

12 22

Re: [anti-abuse-wg] anti-abuse-wg Digest, Vol 8, Issue 9
by Wout de Natris 13 Apr '12

13 Apr '12

"Re: Contents of anti-abuse-wg digest..." Why does this discussion take so many words and arguments? 1. Primarily RIPE NCC needs or at least should need a proper overview of who its members are for several reasons that all have to do with internal processes like reaching out, billing and maintaining correct records, in short common business practice. 2. There is an abuse function for well ... abuse, so members can reach out to each other and amend whatever goes wrong. All this isn't strange or weird, but normal practice for any company, club, association, etc. As soon as an address isn't correct the company, club, association, university, etc. reaches out to the customer, member, student concerned in order to get new relevant data, so it can do billing, maintenance of records, send news, etc. If the customer, member, et al, does not respond, steps are taken to terminate the relation. This is common practice to any company, club, association, etc. and has, primarily, nothing to do with law enforcement of any kind, but with customer/member relations, correct records, due payment, etc. So how come that as soon as this discussion is about the Internet, whether domain name registrations or in this case IP addresses, this totally normal form of doing business is denied as being standard practice? If data is not correct and there is no way the, in this case RIPE NCC, member can be found, it is not so strange that, after a published notice with a due time frame, a relation is terminated. Certainly in a period of scarcity in IPv4 addresses, this should be common practice. (And if it happens to concern a criminal organisation, they won't show up any way. All others will within about 2 seconds of termination.) So if correct data is standard practice and law enforcement needs them for whatever reason, they can access this data either through Whois of through correct proceedings in the Dutch law. Like it should be. Correct data saves money in the end, for all concerned, and makes becoming a member less attractive for individuals or organisations that most of us agree don't need a place on the internet. I don't think LEAs ask for more than that, but as a RIPE member I would look at my own organisation first. LEAs need to deal with LIRs more than an RIR, I'd guess, so assist them in finding these LIRs. Wout > From: anti-abuse-wg-request(a)ripe.net > Subject: anti-abuse-wg Digest, Vol 8, Issue 9 > To: anti-abuse-wg(a)ripe.net > Date: Wed, 11 Apr 2012 16:13:31 +0200 > > Send anti-abuse-wg mailing list submissions to > anti-abuse-wg(a)ripe.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ripe.net/mailman/listinfo/anti-abuse-wg > or, via email, send a message with subject or body 'help' to > anti-abuse-wg-request(a)ripe.net > > You can reach the person managing the list at > anti-abuse-wg-owner(a)ripe.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of anti-abuse-wg digest..." > > > Today's Topics: > > 1. Re: Introducing the RIPE NCC Report Form (julien tayon) > 2. Re: current business practices (Frank Gadegast) > 3. Re: Introducing the RIPE NCC Report Form (Chris Heinze) > 4. Re: current business practices (Gert Doering) > 5. Re: current business practices (Michele Neylon :: Blacknight) > 6. Re: current business practices (Suresh Ramasubramanian) > 7. Re: current business practices (Frank Gadegast) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 11 Apr 2012 15:49:01 +0200 > From: julien tayon <julien(a)tayon.net> > Subject: Re: [anti-abuse-wg] Introducing the RIPE NCC Report Form > To: Brian Nisbet <brian.nisbet(a)heanet.ie> > Cc: anti-abuse-wg(a)ripe.net > Message-ID: > <CAFpLVkyZQb0W3iCTMuq_uK3fBysQf8gHt8sP23MLypu3P4hriw(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > 2012/4/11 Brian Nisbet <brian.nisbet(a)heanet.ie>: > > Chris, > > > > "Chris" wrote the following on 11/04/2012 11:03: > >> > >> On 04/10/2012 05:18 PM, Joe St Sauver wrote: > >>> > >>> Maintenance of the database documenting who's been allocated/assigned > >>> space is *core* to RIPE's mission. > >> > >> > >> simply wrong. > >> ripe's core is allocation. that's what they do. your mission is your > >> private error. > > > > > Ripe's core is at least to provide **change management** over > contact on allocation of internet resources (IP, AS) so that > stakeholder's can cooperate, since internet protocols relies on swift > cooperation between entities. Imagine a world in which you cannot > reach a LIR or RIR having wrong BGP rules ? > > Furthermore, RIPE NCC is bound by its contract with ICANN in its > mission of allocating resources. I think reading the actual contract > might settle the topic pretty fast. > > Since I don't have the contract under my eyes right now, I will make a > simple reasoning based on public informations and personnal > experience. > > Let's stick to the common sense of database first : > *Data accuracy is the most important property of a database.* Ripe NCC > is entitled to manage the whois database, therefore it is in their > mission to ensure DB integrity. > > If it is not convincing enough, let's remember data accuracy is > considered by ICANN as a **MUST DO** for delegated entities (both for > gTLD and resources). > Just search ICANN web sites and you'll have extended papers explaining > why accuracy matters, and how this responsability is also delegated. > http://www.icann.org/en/gsearch/accuracy > > In a world without accurate whois contact it will be the the > strongest's rule that shall prevail. > > What tickles me is how can RIPE NCC bill instances they don't have the > **accurate** contacts ? Are there 2 DBs one for billing (with accurate > data) and another one for public access with inaccurate data ? > > RIPE NCC cant choose the parts it likes in its delegated mission from > ICANN. A contract is a contract and RIPE NCC is bound by its duties > regarding ICANN. If ICANN states RIPE NCC MUST have accurates data, > and MUST enforce internet policies I cannot see how RIPE NCC or RIPE > can decide it is does not fall into their responsabilities. > > Now, all everybody needs to know : > * what level of accuracy ICANN can realistcly expect from its delegates ? > * what are the internet policies ICANN mentions ? > > Cheers. > > -- > Jul > Experienced freelance for years (having worked for ISP). > > > > ------------------------------ > > Message: 2 > Date: Wed, 11 Apr 2012 16:08:11 +0200 > From: Frank Gadegast <ripe-anti-spam-wg(a)powerweb.de> > Subject: Re: [anti-abuse-wg] current business practices > To: "anti-abuse-wg(a)ripe.net" <anti-abuse-wg(a)ripe.net> > Message-ID: <4F85904B.8090203(a)powerweb.de> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > V > > >> > subpoena by deleting the wrong AS object from the database > > > >> ;o) > > > > > > > > Heh. ACK on the role. But I was thinking towards urging the ISP itself to take action (once you HAVE contacted them) on the abuse complaints. That's where the pressure of a lea agency can come in handy, if such a regulator is available. > > > > > > Well, the only possibility would be the police. > They do care here in Germany are kind of > technical disadvanced :o( > > There is some organizations this ISP is a member of > (like the ECO), and they have also a abuse clearing > board, but that one isnt really useful because > it never did anything against their members ... > > And why should they do something, they are not > responsible for the resources ... > > > Kind regards, Frank > > > > > Pepijn > > > > +++++++++++++++++++++++++++++++++++++++++++++ > > > > Disclaimer > > > > Dit e-mailbericht kan vertrouwelijke informatie bevatten of informatie die is beschermd door een beroepsgeheim. > > > > Indien dit bericht niet voor u is bestemd, wijzen wij u erop dat elke vorm van verspreiding, vermenigvuldiging > > > > of ander gebruik ervan niet is toegestaan. > > > > Indien dit bericht blijkbaar bij vergissing bij u terecht is gekomen, verzoeken wij u ons daarvan > > > > direct op de hoogte te stellen via tel.nr 070 315 3500 of e-mail mailto:mail@opta.nl en het bericht te vernietigen. > > > > Dit e-mailbericht is uitsluitend gecontroleerd op virussen. > > > > OPTA aanvaardt geen enkele aansprakelijkheid voor de feitelijke inhoud en juistheid van dit bericht en er kunnen > > > > geen rechten aan worden ontleend. > > > > > > > > > > > > This e-mail message may contain confidential information or information protected by professional privilege. > > > > If it is not intended for you, you should be aware that any distribution, copying or other form of use of > > > > this message is not permitted. > > > > If it has apparently reached you by mistake, we urge you to notify us by phone +31 70 315 3500 > > > > or e-mail mailto:mail@opta.nl and destroy the message immediately. > > > > This e-mail message has only been checked for viruses. > > > > The accuracy, relevance, timeliness or completeness of the information provided cannot be guaranteed. > > > > OPTA expressly disclaims any responsibility in relation to the information in this e-mail message. > > > > No rights can be derived from this message. > > > > > > > > > > > > > -- > > Mit freundlichen Gruessen, > -- > MOTD: "have you enabled SSL on a website or mailbox today ?" > -- > PHADE Software - PowerWeb http://www.powerweb.de > Inh. Dipl.-Inform. Frank Gadegast mailto:frank@powerweb.de > Schinkelstrasse 17 fon: +49 33200 52920 > 14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921 > ====================================================================== > > > > > ------------------------------ > > Message: 3 > Date: Wed, 11 Apr 2012 14:49:13 +0200 > From: Chris Heinze <Chris.Heinze(a)consol.de> > Subject: Re: [anti-abuse-wg] Introducing the RIPE NCC Report Form > To: anti-abuse-wg(a)ripe.net > Message-ID: <4F857DC9.8060905(a)consol.de> > Content-Type: text/plain; charset=UTF-8 > > On 04/11/2012 02:13 PM, Brian Nisbet wrote: > >> ripe's core is allocation. that's what they do. your mission is your private error. > > > > http://www.ripe.net/lir-services/ncc/functions > > right, that sums it up nicely, thanks. > > > Once all of v4 space is allocated (soon now, soon), the primary job of the NCC and the other four RIRs will be keeping a good registry. > > ripe's job isn't defined by and doesn't depend on whether or not v4 space is completely allocated (which it btw probably never will). > keeping a good registry is as explained a service kindly provided by ripe to help - and it did that since the beginning. > > regards, > > Chris > > > > ------------------------------ > > Message: 4 > Date: Wed, 11 Apr 2012 15:29:17 +0200 > From: Gert Doering <gert(a)space.net> > Subject: Re: [anti-abuse-wg] current business practices > To: Suresh Ramasubramanian <ops.lists(a)gmail.com> > Cc: shane(a)time-travellers.org, Brian Nisbet <brian.nisbet(a)heanet.ie>, > anti-abuse-wg(a)ripe.net, Tobias Knecht <tk(a)abusix.com>, "Michele Neylon > :: Blacknight" <michele(a)blacknight.ie>, Laura Cobley <laura(a)ripe.net>, > Florian Weimer <fw(a)deneb.enyo.de>, Frank Gadegast > <ripe-anti-spam-wg(a)powerweb.de>, Gert Doering <gert(a)space.net> > Message-ID: <20120411132917.GN84425(a)Space.Net> > Content-Type: text/plain; charset="us-ascii" > > hi, > > On Wed, Apr 11, 2012 at 06:50:02PM +0530, Suresh Ramasubramanian wrote: > > On Wed, Apr 11, 2012 at 6:32 PM, Frank Gadegast > > <ripe-anti-spam-wg(a)powerweb.de> wrote: > > > will receives this could please make a > > > telnet mamba.ripe.net 25 > > > from some IPs he own (best would be not using his or her usual IP, > > > if he or she likes, lets see how big that problem really > > > is, thats why I have to mail the most active people directly). > > > > suresh@frodo 03:54:25 :~$ telnet mamba.ripe.net smtp > > Trying 2001:67c:2e8:11::c100:1328... > > Trying 193.0.19.40... > > telnet: Unable to connect to remote host: Connection refused > > > > Things seem to be RIPE for a change eh? > > So, what exactly causes the assumption that mamba is supposed to be > reachable from the outside, on Port 25? > > $ host -t mx ripe.net > ripe.net mail is handled by 250 postlady.ripe.net. > ripe.net mail is handled by 200 postgirl.ripe.net. > > Now, obviously, expecting anti-spammers to understand about MX records > and how to read Received: lines might be asking for a bit much... > > Gert Doering > -- NetMaster > -- > have you enabled IPv6 on something today...? > > SpaceNet AG Vorstand: Sebastian v. Bomhard > Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann > D-80807 Muenchen HRB: 136055 (AG Muenchen) > Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279 >

6 6

Re: [anti-abuse-wg] Analysis of the Legal Framework and Procedures Proposed by the Data Protection Task Force
by lists＠help.org 13 Apr '12

13 Apr '12

There are companies now that download the various whois databases and repackage and resell the data. One company DomainTools.com has their parent company in the EU in Luxembourg. How is it that they download all this data and resell it apparently without a problem. If it was illegal why they don't get prosecuted? This "legal framework" doesn't address any of that. DomainTool.com has filed a lawsuit in the US federal courts asking them to rule that downloading and selling whois data is illegal. the lawsuit in question involves data from Tucows in Canada so it is unclear how a US court can rule on that. In any case none of this stuff in discussed in the legal framework paper. Are there plans to take legal action against DomainTools.com for selling this data? If not, why not? Why are there restrictions on others if some companies are downloading and selling this data anyway? Just like you can't force people to answer their abuse mailboxes I don't see how you can force people to use (or not to use) data in a certain way after it is made public. http://domainnamewire.com/2012/04/06/domain-tools-files-preemptive-lawsuit/

3 6

Analysis of the Legal Framework and Procedures Proposed by the Data Protection Task Force
by Athina Fragkouli 12 Apr '12

12 Apr '12

Dear colleagues, Current rules regarding bulk access to the data held in the RIPE Database were set based on the work of the Data Protection Task Force, which concluded its work in 2011. At that time, the DPTF published a report on it's activities and outcomes, which was published here: https://www.ripe.net/ripe/groups/tf/dp/report-of-the-ripe-data-protection-t… Recent discussion on this list has suggested that a clear overview of the legal background to the framework and procedures proposed by the DPTF may help foster better community understanding of the RIPE Database rules and the justification behind them. In the interests of transparency and understanding, the RIPE NCC has produced a report that provides the legal analysis and background of all proposals made by the DPTF. This report, which is intended to complement the original DPTF report, is available now at: https://www.ripe.net/data-tools/support/documentation/legal-framework-and-p… Kind regards, Athina Fragkouli Legal Counsel RIPE NCC

2 1

Re: [anti-abuse-wg] Introducing the RIPE NCC Report Form
by Joe St Sauver 12 Apr '12

12 Apr '12

Chris commented: #1) if you have a legal problem, go to a legal organisation ("police"), not #ripe. clarify your legal issues there. ripe isn't the place for this. Errors in registration details are not a police matter. Errors in registration details ARE directly germane to RIPE's remit as administrator of number resources, a function it provides for those in its region on behalf of the worldwide Internet community. #2) i generally appreciate ripe ncc's efforts to provide adequate aid in case of #any problems - nevertheless it has it's functions and tasks to stick to, #letting sbdy use it to mess with ripe-external stuff Maintenance of the database documenting who's been allocated/assigned space is *core* to RIPE's mission. #non-ripe-charged 'ripe-extraterritorials' creating lengthy flamey #threats as to what kind of services they "demand" from ripe, i btw #find - err - "curious"... Note that by RIPE policy, participation in RIPE Working Groups (including the Anti-Abuse Working Group) is open to all, which is, I believe, an appropriate reflection of the fact that RIPE-allocated resources can and do have an impact on users worldwide. Of course, if you take issue with that policy, you're free to propose a new policy that would change that. #3) if the complainant isn't prepared, able, or willing to express his complaint #against the alleged suspect, this probably already says it all... (ok so much: #then ncc shouldn't play bully for some troll) The question on the table was a simple one: what should be required of a party notifying RIPE of a data inaccuracy in the existing database. Should the notifying party be required to demonstrate exhaustion of all possible self-notification channels before referring the matter to RIPE as a "last resort?" No. A good Samaritan volunteer reporters has no obligation to do RIPE's work for them, and any attempt to impose arbitrary additional obligations on voluntary reporters is misplaced and inappropriate, and shows a lack of respect for the community member making that report. I see nothing wrong or inappropriate about expecting a RIR to maintain accurate records concerning the resouces it oversees, nor do I see how that makes anyone a "troll." Regards, Joe

11 18

Re: [anti-abuse-wg] Introducing the RIPE NCC Report Form
by Leo Vegoda 12 Apr '12

12 Apr '12

Hi Frank, This message is copied to the list, as requested. Frank Gadegast wrote: [...] > Lets ask me one thing (simply because you have an iconn email address): > is ICANN forcing the RIRs to have a public whois database by CONTRACT > and are the registries forced to have up-to-date and validated data in it ? > > Could you please point that out on the list ? I do not believe there is currently a contract between ICANN and the NRO or individual RIRs. In 2007, ICANN and the NRO agreed an exchange of letters. In ICANN's letter to the NRO it stated that it seeks "to further enhance our relationship for the mutual benefit of our organizations and respective communities. For that matter we wish and will seek to establish an appropriate legal arrangement within one (1) year from the date of this letter." I do not believe that arrangement has been established. You can find the announcement about the exchange of letters on the ICANN web site, here: http://www.icann.org/en/news/announcements/announcement-09nov07-en.htm The letters themselves are published on the correspondence pages but that announcement places them in a single page, which is more convenient to read. I expect the "Review of the ASO" document, which is currently in the second half of the public comment period, will have a fuller description of the relationship between the NRO and ICANN: http://www.icann.org/en/news/public-comment/aso-review-16mar12-en.htm Kind regards, Leo Vegoda

1 0

Re: [anti-abuse-wg] Introducing the RIPE NCC Report Form
by Joe St Sauver 11 Apr '12

11 Apr '12

Florian commented: #I looked at "Incorrect contact information in the RIPE Database", and #"I confirm that I have reported the incorrect information to all of #the contacts listed in the relevant object" is a required checkbox. # #This seems to require that complainants try postal addresses, phone #and fax numbers before reporting errors in email addresses. Is this #really your goal? Isn't this a step backwards? I agree. >From my POV, each data element should be treated independently. The existence of a valid FAX number, for example, should not offset or eliminate the importance (or the reportability) of working to correct an invalid/non-deliverable email address. Similarly, having found an invalid field in the whois, the reporter's "responsibility" should be considered discharged upon their identifying and reporting that data to RIPE. They should not be expected to exhaust all potential contact methods, or to make multiple attempts to the broken contact channel, or to hypothetically attempt to visit the listed address in person, :-), just in order to be eligible to report a problem with data of record. The goal should be correcting potentially bad data, not making it hard to report bad data or shifting work back upon public spirited community volunteers. Regards, Joe

5 6

Re: [anti-abuse-wg] current business practices
by Frank Gadegast 11 Apr '12

11 Apr '12

V >> subpoena by deleting the wrong AS object from the database > >> ;o) > > > > Heh. ACK on the role. But I was thinking towards urging the ISP itself to take action (once you HAVE contacted them) on the abuse complaints. That's where the pressure of a lea agency can come in handy, if such a regulator is available. > > Well, the only possibility would be the police. They do care here in Germany are kind of technical disadvanced :o( There is some organizations this ISP is a member of (like the ECO), and they have also a abuse clearing board, but that one isnt really useful because it never did anything against their members ... And why should they do something, they are not responsible for the resources ... Kind regards, Frank > > Pepijn > > +++++++++++++++++++++++++++++++++++++++++++++ > > Disclaimer > > Dit e-mailbericht kan vertrouwelijke informatie bevatten of informatie die is beschermd door een beroepsgeheim. > > Indien dit bericht niet voor u is bestemd, wijzen wij u erop dat elke vorm van verspreiding, vermenigvuldiging > > of ander gebruik ervan niet is toegestaan. > > Indien dit bericht blijkbaar bij vergissing bij u terecht is gekomen, verzoeken wij u ons daarvan > > direct op de hoogte te stellen via tel.nr 070 315 3500 of e-mail mailto:mail@opta.nl en het bericht te vernietigen. > > Dit e-mailbericht is uitsluitend gecontroleerd op virussen. > > OPTA aanvaardt geen enkele aansprakelijkheid voor de feitelijke inhoud en juistheid van dit bericht en er kunnen > > geen rechten aan worden ontleend. > > > > > > This e-mail message may contain confidential information or information protected by professional privilege. > > If it is not intended for you, you should be aware that any distribution, copying or other form of use of > > this message is not permitted. > > If it has apparently reached you by mistake, we urge you to notify us by phone +31 70 315 3500 > > or e-mail mailto:mail@opta.nl and destroy the message immediately. > > This e-mail message has only been checked for viruses. > > The accuracy, relevance, timeliness or completeness of the information provided cannot be guaranteed. > > OPTA expressly disclaims any responsibility in relation to the information in this e-mail message. > > No rights can be derived from this message. > > > > > -- Mit freundlichen Gruessen, -- MOTD: "have you enabled SSL on a website or mailbox today ?" -- PHADE Software - PowerWeb http://www.powerweb.de Inh. Dipl.-Inform. Frank Gadegast mailto:frank@powerweb.de Schinkelstrasse 17 fon: +49 33200 52920 14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921 ======================================================================

1 0

Re: [anti-abuse-wg] current business practices
by Frank Gadegast 11 Apr '12

11 Apr '12

Vissers, Pepijn wrote: > Hi Frank, Hi, > > > > Interesting story. Here in NL, we act as LEA towards an ISP if the abuse we see is related to spam and/or malware (because that is our (OPTA) function as telco regulator). In most cases, abuse reports from a law enforcement agency tend to be picked up with a little more urgency so the strategy is quite effective. > > > > If the ISP is non-cooperative, we might choose to apply a little more pressure by a subpoena of some kind. Usually applying such pressure results in a positively correlated attitude towards handling said abuse tickets. The strategy is derived from the theory of 'responsive regulation' by Braithwait. > > > > Do you have such a regulator (with investigative capabilities) who you could team up with in DE? Surely not. Its the role of RIPE NCC (too my understanding) to keep their database up-to-date. subpoena by deleting the wrong AS object from the database ;o) Pretty simple ... Kind regards, Frank > > > > Kind regards, > > Pepijn > > > >> -----Oorspronkelijk bericht----- > >> Van: anti-abuse-wg-bounces(a)ripe.net [mailto:anti-abuse-wg- > >> bounces(a)ripe.net] Namens Frank Gadegast > >> Verzonden: woensdag 11 april 2012 15:18 > >> Aan: anti-abuse-wg(a)ripe.net > >> Onderwerp: Re: [anti-abuse-wg] current business practices > >> > >> Laura Cobley wrote: > >>> Dear Florian and all, > >> > >> Hi, > >> > >> (some details from our current experiences with RIPE NCC and accuracy > >> of the RIPE objects) > >> > >> we currently have one case where a really big German cablenet ISP is > >> having exacly one abuse-eMail address for their tech-c, abuse-mailbox > >> and admin-c, for all their objects. > >> > >> And this one email has a domain, what does not belong to the ISP > >> anymore, since November 2011, its currently owned by a domain grabber, > >> because the ISP deleted the domain on purpose (on behalf of a change in > >> the company name years ago). > >> There is no other working contact information (phone lets you end up at > >> their hotline where they have absolutly no idea about abuse), snail > >> mail is no option, fax number is not supplied. > >> > >> We tried mailing there peering contact, their normal customer email > >> from their website, filled their online feedback form and then opened a > >> normal ticket at RIPE NCC, were just told to open another ticket at > >> RIPE NCC and invested about 5 hours already describing the problem at > >> RIPE NCC. > >> Simply no chance, RIPE NCC is responding to tickets on a daily basis, > >> even during business hours (jesus, we will respond in about 5 minutes > >> if something serious like that will happen to our networks). > >> The interest at the RIPE NCC to fix database problems does not seem to > >> have any priority. > >> > >> Ah, I forgot: > >> the maillist server mamba.ripe.net has technical problems during the > >> last 3 weeks, we opened tickets for that as well and even got a > >> response once, still not fixed, the maillist server is probably not > >> reacheable for 90% of the members ... whoever will receives this could > >> please make a telnet mamba.ripe.net 25 from some IPs he own (best would > >> be not using his or her usual IP, if he or she likes, lets see how big > >> that problem really is, thats why I have to mail the most active people > >> directly). > >> > >> -------- > >> Little update: seems like RIPE NCC changed the maillist server to > >> postgirl.ripe.net and that one works. > >> Looks like they had to change this in a hurry, because the old server > >> did hang in the nameserver caches quite long (great, that I have to > >> find that out myself, instead that > >> somebody from the RIPE NCC is simply telling me that or posting > >> to the list). > >> -------- > >> Sorry, if nearly the same email comes twice now ... have to test it. > >> > >> So: abuse does not have priority in a lot of peoples heads those days, > >> even when they tell you that daily ... > >> > >> (we have about 100 abuse incidents with that ISP monthly and the ISP > >> even resides in the same country than we are, but its still, if they > >> reside on the other side of the moon, maybe I should demonstrate > >> if front of the office building with a big sign saying: > >> "you dont have a working abuse appartment") > >> > >> > >> Kind regards, Frank > >>> > >>> Over time, contact information in the RIPE Database can become > >>> outdated due to staffing changes, oversight and lack of knowledge on > >>> the part of the maintainer. Bringing the irregularity directly to the > >>> attention of this maintainer can be the quickest way to get it fixed. > >>> > >>> If you subsequently experience difficulties with this, we can help > >> you > >>> to get in touch with the maintainer by forwarding your report to the > >>> person responsible for the Internet number resource registration. > >>> Handling reports is a normal part of our operations within the RIPE > >>> NCC and the report form makes it easier to get in touch with us. > >>> > >>> We ask you to include information such as mail delivery failure > >>> notices and copies of emails with headers, which clearly show the > >>> problem and the subsequent difficulties you are having. These help to > >>> substantiate the report. Our aim is to work together with you to > >>> further improve the quality of the data in the Internet number > >> resource registry. > >>> > >>> Best regards, > >>> > >>> Laura Cobley > >>> RIPE NCC > >>> > >>> On 4/6/12 8:45 PM, Florian Weimer wrote: > >>>> * Laura Cobley: > >>>> > >>>>> Using this form, you can now easily report various issues, > >> including > >>>>> abnormalities in Internet number resource registrations, to us for > >>>>> further investigation. > >>>> > >>>> I looked at "Incorrect contact information in the RIPE Database", > >> and > >>>> "I confirm that I have reported the incorrect information to all of > >>>> the contacts listed in the relevant object" is a required checkbox. > >>>> > >>>> This seems to require that complainants try postal addresses, phone > >>>> and fax numbers before reporting errors in email addresses. Is this > >>>> really your goal? Isn't this a step backwards? > >>>> > >>> > >>> > >>> > >> > >> > >> -- > >> > >> Mit freundlichen Gruessen, > >> -- > >> MOTD: "have you enabled SSL on a website or mailbox today ?" > >> -- > >> PHADE Software - PowerWeb http://www.powerweb.de > >> Inh. Dipl.-Inform. Frank Gadegast mailto:frank@powerweb.de > >> Schinkelstrasse 17 fon: +49 33200 52920 > >> 14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921 > >> ====================================================================== > >> > >> > > > > +++++++++++++++++++++++++++++++++++++++++++++ > > Disclaimer > > Dit e-mailbericht kan vertrouwelijke informatie bevatten of informatie die is beschermd door een beroepsgeheim. > > Indien dit bericht niet voor u is bestemd, wijzen wij u erop dat elke vorm van verspreiding, vermenigvuldiging > > of ander gebruik ervan niet is toegestaan. > > Indien dit bericht blijkbaar bij vergissing bij u terecht is gekomen, verzoeken wij u ons daarvan > > direct op de hoogte te stellen via tel.nr 070 315 3500 of e-mail mailto:mail@opta.nl en het bericht te vernietigen. > > Dit e-mailbericht is uitsluitend gecontroleerd op virussen. > > OPTA aanvaardt geen enkele aansprakelijkheid voor de feitelijke inhoud en juistheid van dit bericht en er kunnen > > geen rechten aan worden ontleend. > > > > > > This e-mail message may contain confidential information or information protected by professional privilege. > > If it is not intended for you, you should be aware that any distribution, copying or other form of use of > > this message is not permitted. > > If it has apparently reached you by mistake, we urge you to notify us by phone +31 70 315 3500 > > or e-mail mailto:mail@opta.nl and destroy the message immediately. > > This e-mail message has only been checked for viruses. > > The accuracy, relevance, timeliness or completeness of the information provided cannot be guaranteed. > > OPTA expressly disclaims any responsibility in relation to the information in this e-mail message. > > No rights can be derived from this message. > > > > > -- Mit freundlichen Gruessen, -- MOTD: "have you enabled SSL on a website or mailbox today ?" -- PHADE Software - PowerWeb http://www.powerweb.de Inh. Dipl.-Inform. Frank Gadegast mailto:frank@powerweb.de Schinkelstrasse 17 fon: +49 33200 52920 14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921 ======================================================================

1 0

Enabling community self-help?
by Shane Kerr 08 Apr '12

08 Apr '12

All, warning: crazy idea time Does it seem like a good idea to provide a way to attach "user comments" to network information? Background... Some people want someone to force ISP's to take responsibility for fixing abuse originating in their networks. The natural place for this enforcement appears to them to be the RIPE NCC (*). Contrariwise, the RIPE NCC is unable to unwilling to change its role from a fundamentally administrative to one that involves setting network usage policies. This involves risks in terms of anti-trust regulators, need to carefully define the limits of control, and setting up what amounts to a industry legal system (with both judges and police). Plus it is hard to get the RIPE NCC membership to support mechanisms which cost them money and limit their freedoms. On the 3rd hand, some people in the RIPE community (including me) also feel that it is very, very difficult to define what the required actions would be in the case of reported abuse. This reporting mechanism itself might indeed be a source of abuse (rivalries between companies could be fought by each accusing the other of hosting criminal activity). Crazy Idea... Lets crowd-source it. Maybe it makes sense to make something like a web forum for each allocated resource, or perhaps for the organization responsible for each. It could be something like a blog article with the contact and other information about each resource, and then a way to post comments about it. So, you might see that ISP ShaNet has working e-mail for abuse, but nobody ever sees any action beyond automated response. Such reports could be useful for people who *can* investigate and do something, such as law enforcement or regulators. A few decades of Internet forums have given us best practices in terms of policing forums for spam and abuse, for evaluating user trustworthiness and helpfulness, and for evaluating the value of individual comments or replies (+1). I think something like this would be within the realm of things that the RIPE NCC could provide. We could link to these pages from the WHOIS results (or go straight there for web queries perhaps). There are lots of web sites which publish consumer evaluations of various companies and products, so this really is not so different. -- Shane (*) Well, normally confused with RIPE (or Ripe). But the RIPE NCC is what they mean.

10 30