Post
Topic
Board Beginners & Help
Re: For Inaba & Аdministrations
by
Clipse
on 24/07/2012, 17:19:14 UTC
Sadly that you didn't find time to check the address at all!

62.33.13.241

 % 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 '62.33.12.0 - 62.33.13.255'

 inetnum: 62.33.12.0 - 62.33.13.255
 netname: TELESETI-PLUS-NET
descr: (MS003389) teleseti plus,
 descr: Pechori, Russia

 country: RU
 admin-c: SAI19-RIPE
 tech-c: SAI19-RIPE
 status: ASSIGNED PA
 mnt-by: TRANSTELECOM-MNT
 source: RIPE # Filtered

 % Information related to '62.33.0.0/20AS20485'

 route: 62.33.0.0/20
 descr: RU-TRANS-TELECOM
 descr: Moscow
 origin: AS20485
 mnt-by: TRANSTELECOM-MNT
 source: RIPE # Filtered

 % This query was served by the RIPE Database Query Service version 1.19 (WHOIS1)


217.150.40.229

 % 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 '217.150.40.0 - 217.150.40.255'

 inetnum: 217.150.40.0 - 217.150.40.255
 netname: TTK-PtP-NET5
 descr: Transtelecom point-to-point interfaces
 country: RU

 admin-c: KTTK-RIPE
 tech-c: KTTK-RIPE
 status: ASSIGNED PA
 remarks: INFRA-AW
 mnt-by: TRANSTELECOM-MNT
 source: RIPE # Filtered

 % Information related to '217.150.32.0/20AS20485'

 route: 217.150.32.0/20
 descr: RU-TRANS-TELECOM-20010213
 origin: AS20485
 mnt-by: TRANSTELECOM-MNT
 source: RIPE # Filtered

 % This query was served by the RIPE Database Query Service version 1.19 (WHOIS2)




Yes, you are a genius, now do this: google for public proxy 217.150.40.229 and you will find that all the summary hits is related to russian public proxy on that ip.

Id go so far to say that if its not used as a public proxy then you likely signed in from some transparent proxy at your home internet connection where the 62.33.13.241 ip is likely related to your static internet IP at whatever company you work.

Damn you figured you would be super clever by making it seem like it is a huge conspiracy, you sir are SCUM.