Skip to content

GSA Proxy scraper - Solidseovps issue

VMartVMart Natural SEO
edited July 2016 in GSA Proxy Scraper
@sven

I am using solidseovps for GSA ser and gsa proxy scrapper, Recently server send violation notice to me in the following report.

Netscan detected from host 89.32.177.12

#

time protocol src_ip src_port dest_ip dest_port

Mon Jul 18 20:41:32 2016 TCP 89.32.177.12 53929 => 88.198.4.0 111
Mon Jul 18 20:41:35 2016 TCP 89.32.177.12 53929 => 88.198.4.0 111
Mon Jul 18 20:42:17 2016 TCP 89.32.177.12 56491 => 88.198.41.24 111
Mon Jul 18 20:42:20 2016 TCP 89.32.177.12 56491 => 88.198.41.24 111
Mon Jul 18 20:41:39 2016 TCP 89.32.177.12 54402 => 88.198.41.25 111
Mon Jul 18 20:41:43 2016 TCP 89.32.177.12 54402 => 88.198.41.25 111
Mon Jul 18 20:44:50 2016 TCP 89.32.177.12 64402 => 88.198.41.26 111
Mon Jul 18 20:44:54 2016 TCP 89.32.177.12 64402 => 88.198.41.26 111
Mon Jul 18 20:43:12 2016 TCP 89.32.177.12 59555 => 88.198.41.27 111
Mon Jul 18 20:43:15 2016 TCP 89.32.177.12 59555 => 88.198.41.27 111
Mon Jul 18 20:44:30 2016 TCP 89.32.177.12 63241 => 88.198.41.28 111
Mon Jul 18 20:44:33 2016 TCP 89.32.177.12 63241 => 88.198.41.28 111
Mon Jul 18 20:43:52 2016 TCP 89.32.177.12 61329 => 88.198.41.29 111
Mon Jul 18 20:43:55 2016 TCP 89.32.177.12 61329 => 88.198.41.29 111
Mon Jul 18 20:43:12 2016 TCP 89.32.177.12 59559 => 88.198.41.30 111
Mon Jul 18 20:43:15 2016 TCP 89.32.177.12 59559 => 88.198.41.30 111
Mon Jul 18 20:42:32 2016 TCP 89.32.177.12 57524 => 88.198.41.31 111
Mon Jul 18 20:42:35 2016 TCP 89.32.177.12 57524 => 88.198.41.31 111
Mon Jul 18 20:44:29 2016 TCP 89.32.177.12 63146 => 88.198.42.0 111
Mon Jul 18 20:44:32 2016 TCP 89.32.177.12 63146 => 88.198.42.0 111
Mon Jul 18 20:42:13 2016 TCP 89.32.177.12 56342 => 88.198.42.1 111
Mon Jul 18 20:42:16 2016 TCP 89.32.177.12 56342 => 88.198.42.1 111
Mon Jul 18 20:42:00 2016 TCP 89.32.177.12 55692 => 88.198.42.2 111
Mon Jul 18 20:42:03 2016 TCP 89.32.177.12 55692 => 88.198.42.2 111
Mon Jul 18 20:41:55 2016 TCP 89.32.177.12 55495 => 88.198.42.3 111
Mon Jul 18 20:41:58 2016 TCP 89.32.177.12 55495 => 88.198.42.3 111
Mon Jul 18 20:44:10 2016 TCP 89.32.177.12 62302 => 88.198.42.4 111
Mon Jul 18 20:44:13 2016 TCP 89.32.177.12 62302 => 88.198.42.4 111
Mon Jul 18 20:41:18 2016 TCP 89.32.177.12 53364 => 88.198.42.5 111
Mon Jul 18 20:41:21 2016 TCP 89.32.177.12 53364 => 88.198.42.5 111
Mon Jul 18 20:43:12 2016 TCP 89.32.177.12 59557 => 88.198.42.6 111
Mon Jul 18 20:43:15 2016 TCP 89.32.177.12 59557 => 88.198.42.6 111
Mon Jul 18 20:44:08 2016 TCP 89.32.177.12 62223 => 88.198.42.7 111
Mon Jul 18 20:44:11 2016 TCP 89.32.177.12 62223 => 88.198.42.7 111
Mon Jul 18 20:43:48 2016 TCP 89.32.177.12 61125 => 88.198.42.8 111
Mon Jul 18 20:43:51 2016 TCP 89.32.177.12 61125 => 88.198.42.8 111
Mon Jul 18 20:42:31 2016 TCP 89.32.177.12 57470 => 88.198.42.9 111
Mon Jul 18 20:42:34 2016 TCP 89.32.177.12 57470 => 88.198.42.9 111
Mon Jul 18 20:45:08 2016 TCP 89.32.177.12 49249 => 88.198.42.10 111
Mon Jul 18 20:45:11 2016 TCP 89.32.177.12 49249 => 88.198.42.10 111
Mon Jul 18 20:44:27 2016 TCP 89.32.177.12 63111 => 88.198.42.11 111
Mon Jul 18 20:44:30 2016 TCP 89.32.177.12 63111 => 88.198.42.11 111
Mon Jul 18 20:42:32 2016 TCP 89.32.177.12 57540 => 88.198.42.12 111
Mon Jul 18 20:42:35 2016 TCP 89.32.177.12 57540 => 88.198.42.12 111
Mon Jul 18 20:44:08 2016 TCP 89.32.177.12 62182 => 88.198.42.13 111
Mon Jul 18 20:44:11 2016 TCP 89.32.177.12 62182 => 88.198.42.13 111
Mon Jul 18 20:42:04 2016 TCP 89.32.177.12 55875 => 88.198.42.14 111
Mon Jul 18 20:42:07 2016 TCP 89.32.177.12 55875 => 88.198.42.14 111
Mon Jul 18 20:44:25 2016 TCP 89.32.177.12 63014 => 88.198.42.15 111
Mon Jul 18 20:44:28 2016 TCP 89.32.177.12 63014 => 88.198.42.15 111
Mon Jul 18 20:42:24 2016 TCP 89.32.177.12 57063 => 88.198.42.16 111
Mon Jul 18 20:42:27 2016 TCP 89.32.177.12 57063 => 88.198.42.16 111
Mon Jul 18 20:45:11 2016 TCP 89.32.177.12 49374 => 88.198.42.17 111
Mon Jul 18 20:45:14 2016 TCP 89.32.177.12 49374 => 88.198.42.17 111
Mon Jul 18 20:43:03 2016 TCP 89.32.177.12 58876 => 88.198.42.18 111
Mon Jul 18 20:43:06 2016 TCP 89.32.177.12 58876 => 88.198.42.18 111
Mon Jul 18 20:43:47 2016 TCP 89.32.177.12 61113 => 88.198.42.19 111
Mon Jul 18 20:43:50 2016 TCP 89.32.177.12 61113 => 88.198.42.19 111
Mon Jul 18 20:41:12 2016 TCP 89.32.177.12 52995 => 88.198.42.20 111
Mon Jul 18 20:41:16 2016 TCP 89.32.177.12 52995 => 88.198.42.20 111
Mon Jul 18 20:45:03 2016 TCP 89.32.177.12 65234 => 88.198.42.21 111
Mon Jul 18 20:45:06 2016 TCP 89.32.177.12 65234 => 88.198.42.21 111
Mon Jul 18 20:40:43 2016 TCP 89.32.177.12 51541 => 88.198.42.22 111
Mon Jul 18 20:40:46 2016 TCP 89.32.177.12 51541 => 88.198.42.22 111
Mon Jul 18 20:42:05 2016 TCP 89.32.177.12 55917 => 88.198.42.23 111
Mon Jul 18 20:42:08 2016 TCP 89.32.177.12 55917 => 88.198.42.23 111
Mon Jul 18 20:40:48 2016 TCP 89.32.177.12 51752 => 88.198.42.24 111
Mon Jul 18 20:40:51 2016 TCP 89.32.177.12 51752 => 88.198.42.24 111
Mon Jul 18 20:40:41 2016 TCP 89.32.177.12 51506 => 88.198.42.25 111
Mon Jul 18 20:40:44 2016 TCP 89.32.177.12 51506 => 88.198.42.25 111
Mon Jul 18 20:43:57 2016 TCP 89.32.177.12 61718 => 88.198.42.26 111
Mon Jul 18 20:44:00 2016 TCP 89.32.177.12 61718 => 88.198.42.26 111
Mon Jul 18 20:42:49 2016 TCP 89.32.177.12 58286 => 88.198.42.27 111
Mon Jul 18 20:42:52 2016 TCP 89.32.177.12 58286 => 88.198.42.27 111
Mon Jul 18 20:42:13 2016 TCP 89.32.177.12 56318 => 88.198.42.28 111
Mon Jul 18 20:42:16 2016 TCP 89.32.177.12 56318 => 88.198.42.28 111
Mon Jul 18 20:41:36 2016 TCP 89.32.177.12 54107 => 88.198.42.29 111
Mon Jul 18 20:41:39 2016 TCP 89.32.177.12 54107 => 88.198.42.29 111
Mon Jul 18 20:42:27 2016 TCP 89.32.177.12 57166 => 88.198.42.30 111
Mon Jul 18 20:42:30 2016 TCP 89.32.177.12 57166 => 88.198.42.30 111
Mon Jul 18 20:43:05 2016 TCP 89.32.177.12 59181 => 88.198.42.31 111
Mon Jul 18 20:43:08 2016 TCP 89.32.177.12 59181 => 88.198.42.31 111
Mon Jul 18 20:42:53 2016 TCP 89.32.177.12 58460 => 88.198.42.32 111
Mon Jul 18 20:42:56 2016 TCP 89.32.177.12 58460 => 88.198.42.32 111
Mon Jul 18 20:42:09 2016 TCP 89.32.177.12 56118 => 88.198.42.33 111
Mon Jul 18 20:42:12 2016 TCP 89.32.177.12 56118 => 88.198.42.33 111
Mon Jul 18 20:41:43 2016 TCP 89.32.177.12 54677 => 88.198.42.34 111
Mon Jul 18 20:41:46 2016 TCP 89.32.177.12 54677 => 88.198.42.34 111
Mon Jul 18 20:40:54 2016 TCP 89.32.177.12 52105 => 88.198.42.35 111
Mon Jul 18 20:40:57 2016 TCP 89.32.177.12 52105 => 88.198.42.35 111
Mon Jul 18 20:41:39 2016 TCP 89.32.177.12 54162 => 88.198.42.36 111
Mon Jul 18 20:43:53 2016 TCP 89.32.177.12 61432 => 88.198.42.37 111
Mon Jul 18 20:43:56 2016 TCP 89.32.177.12 61432 => 88.198.42.37 111
Mon Jul 18 20:44:49 2016 TCP 89.32.177.12 64335 => 88.198.42.38 111
Mon Jul 18 20:44:52 2016 TCP 89.32.177.12 64335 => 88.198.42.38 111
Mon Jul 18 20:41:23 2016 TCP 89.32.177.12 53565 => 88.198.42.39 111
Mon Jul 18 20:41:26 2016 TCP 89.32.177.12 53565 => 88.198.42.39 111
Mon Jul 18 20:42:21 2016 TCP 89.32.177.12 56803 => 88.198.42.40 111
Mon Jul 18 20:42:24 2016 TCP 89.32.177.12 56803 => 88.198.42.40 111
Mon Jul 18 20:41:24 2016 TCP 89.32.177.12 53592 => 88.198.42.41 111
Mon Jul 18 20:41:27 2016 TCP 89.32.177.12 53592 => 88.198.42.41 111
Mon Jul 18 20:41:28 2016 TCP 89.32.177.12 53773 => 88.198.42.42 111
Mon Jul 18 20:41:31 2016 TCP 89.32.177.12 53773 => 88.198.42.42 111
Mon Jul 18 20:44:59 2016 TCP 89.32.177.12 64835 => 88.198.42.43 111
Mon Jul 18 20:45:02 2016 TCP 89.32.177.12 64835 => 88.198.42.43 111
Mon Jul 18 20:43:13 2016 TCP 89.32.177.12 59668 => 88.198.42.44 111
Mon Jul 18 20:43:16 2016 TCP 89.32.177.12 59668 => 88.198.42.44 111
Mon Jul 18 20:43:23 2016 TCP 89.32.177.12 60147 => 88.198.42.45 111
Mon Jul 18 20:43:26 2016 TCP 89.32.177.12 60147 => 88.198.42.45 111
Mon Jul 18 20:40:38 2016 TCP 89.32.177.12 51353 => 88.198.42.46 111
Mon Jul 18 20:40:41 2016 TCP 89.32.177.12 51353 => 88.198.42.46 111
Mon Jul 18 20:40:48 2016 TCP 89.32.177.12 51714 => 88.198.42.47 111
Mon Jul 18 20:40:51 2016 TCP 89.32.177.12 51714 => 88.198.42.47 111
Mon Jul 18 20:41:08 2016 TCP 89.32.177.12 52849 => 88.198.42.48 111
Mon Jul 18 20:41:11 2016 TCP 89.32.177.12 52849 => 88.198.42.48 111
Mon Jul 18 20:44:38 2016 TCP 89.32.177.12 63823 => 88.198.42.49 111
Mon Jul 18 20:44:41 2016 TCP 89.32.177.12 63823 => 88.198.42.49 111
Mon Jul 18 20:42:25 2016 TCP 89.32.177.12 57120 => 88.198.42.50 111
Mon Jul 18 20:42:28 2016 TCP 89.32.177.12 57120 => 88.198.42.50 111
Mon Jul 18 20:42:18 2016 TCP 89.32.177.12 56650 => 88.198.42.51 111
Mon Jul 18 20:42:21 2016 TCP 89.32.177.12 56650 => 88.198.42.51 111
Mon Jul 18 20:42:22 2016 TCP 89.32.177.12 56661 => 88.198.42.52 111
Mon Jul 18 20:40:50 2016 TCP 89.32.177.12 51838 => 88.198.42.53 111
Mon Jul 18 20:40:53 2016 TCP 89.32.177.12 51838 => 88.198.42.53 111
Mon Jul 18 20:44:59 2016 TCP 89.32.177.12 64844 => 88.198.42.54 111
Mon Jul 18 20:45:02 2016 TCP 89.32.177.12 64844 => 88.198.42.54 111
Mon Jul 18 20:42:37 2016 TCP 89.32.177.12 57797 => 88.198.42.55 111
Mon Jul 18 20:42:40 2016 TCP 89.32.177.12 57797 => 88.198.42.55 111
Mon Jul 18 20:44:57 2016 TCP 89.32.177.12 64715 => 88.198.42.56 111
Mon Jul 18 20:45:00 2016 TCP 89.32.177.12 64715 => 88.198.42.56 111
Mon Jul 18 20:42:16 2016 TCP 89.32.177.12 56460 => 88.198.42.57 111
Mon Jul 18 20:42:19 2016 TCP 89.32.177.12 56460 => 88.198.42.57 111
Mon Jul 18 20:40:46 2016 TCP 89.32.177.12 51677 => 88.198.42.58 111
Mon Jul 18 20:40:49 2016 TCP 89.32.177.12 51677 => 88.198.42.58 111
Mon Jul 18 20:44:49 2016 TCP 89.32.177.12 64338 => 88.198.42.59 111
Mon Jul 18 20:44:52 2016 TCP 89.32.177.12 64338 => 88.198.42.59 111
Mon Jul 18 20:44:23 2016 TCP 89.32.177.12 62845 => 88.198.42.60 111
Mon Jul 18 20:44:26 2016 TCP 89.32.177.12 62845 => 88.198.42.60 111
Mon Jul 18 20:42:30 2016 TCP 89.32.177.12 57431 => 88.198.42.61 111
Mon Jul 18 20:42:33 2016 TCP 89.32.177.12 57431 => 88.198.42.61 111
Mon Jul 18 20:44:40 2016 TCP 89.32.177.12 63948 => 88.198.42.62 111
Mon Jul 18 20:44:43 2016 TCP 89.32.177.12 63948 => 88.198.42.62 111
Mon Jul 18 20:44:34 2016 TCP 89.32.177.12 63429 => 88.198.42.63 111
Mon Jul 18 20:44:37 2016 TCP 89.32.177.12 63429 => 88.198.42.63 111
Mon Jul 18 20:44:20 2016 TCP 89.32.177.12 62721 => 88.198.42.64 111
Mon Jul 18 20:44:23 2016 TCP 89.32.177.12 62721 => 88.198.42.64 111
Mon Jul 18 20:43:10 2016 TCP 89.32.177.12 59496 => 88.198.42.65 111
Mon Jul 18 20:43:13 2016 TCP 89.32.177.12 59496 => 88.198.42.65 111
Mon Jul 18 20:42:54 2016 TCP 89.32.177.12 58519 => 88.198.42.66 111

Comments

  • s4nt0ss4nt0s Houston, Texas
    edited July 2016
    Were you port scanning or just using the software as normal? If port scanning, might need to check the option to use a proxy while port scanning. Some hosts don't allow port scanning or you need to be on a specific server location for them to allow it.
  • SvenSven www.GSA-Online.de
    Could be some proxy source that gave the IP and port as possible proxy and so it tries to test that.
  • VMartVMart Natural SEO

    1) How can I find proxy source that gave IP address please suggest I'm using gsa proxy scraper how to find out this type of proxy source.
    2) If I purchase and use gsa proxy scraper How can I overcome the violation problem in the server please give the proper settings to avoid violation problem.
  • SvenSven www.GSA-Online.de
    1) I guess only I can get you that info when you send me all your proxy_sites folder packed.
    2) you can add such ips to the blacklist ... but then it is already happened though.
  • VMartVMart Natural SEO
    1) How can I get proxy_sites folder from gsa proxy scrapper. An which email contact I can send the details to you.

    2) How ca I blacklist such ips.
  • SvenSven www.GSA-Online.de
    1) it's located in C:\Users\<login>\AppData\Roaming\proxy_scraper\proxy_sites -> upload it somewhere and send the link in pm
    2) Have to think about it once I find out why this source does this.
  • VMartVMart Natural SEO
    https://drive.google.com/folderview?id=0B2yFbFgUfyNPaE5ha1dnOVRVVlE&usp=sharing
  • SvenSven www.GSA-Online.de
    didn'T find it in there...i have no idea who did that port scan.
  • VMartVMart Natural SEO
    @Sven

    Please this link

  • VMartVMart Natural SEO
    edited July 2016
    @Sven
    I Have attached proxy_sites.rar folder in media fire, Can you able to access it, please reply.
Sign In or Register to comment.