How can I continue the scan from where it left off?

IvanGlinkin / Fast-Google-Dorks-Scan

The OSINT project, the main idea of which is to collect all the possible Google dorks search combinations and to find the information about the specific web-site: common admin panels, the widespread file types and path traversal. The 100% automated.

1.46k stars 244 forks source link

How can I continue the scan from where it left off? #13

Open ianitow opened 1 year ago

ianitow commented 1 year ago

First of all, congratulations on the tool. Very good.

I would like to know if there is any way to continue from where the script left off, to avoid having to start from the beginning.

7MinSec commented 1 year ago

Just adding a +1 to this request. I ran this tool for the first time today and it's great, but now Google thinks I'm a bot and I would love to be able to resume this enumeration once that issue clears.

IvanGlinkin commented 1 year ago

Evening guys. Unfortunately the only way to do it fully legally - get the API Token and request without the time delay as well as to be blocked. We added the proxy feature so you can put your proxy to bypass limitations. Another possible solution, which I'm using - switch on the VPN with changing the IP. Basically you can get the instance from AWS, launch FGDS and change the IP in case it's blocked. Regards, Ivan

7MinSec commented 1 year ago

Hi Ivan,

Thanks for your response! I have a ProtonVPN account and found per their cli instructions that you can do this to rotate to a random VPN endpoint:

protonvpn-cli c -r

I'd love the ability to insert this command for every X number of Google Dorks your script searches for. Or, maybe it could issue this command if it looks like we've been banned.

Unfortunately I'm a python newb and don't know where I would put this. It seems like maybe I put it where the Google thinks you are a robot part is? But then I'd basically want the ProtonVPN command to run and then the dorking to resume. Could you help with this?

7MinSec commented 1 year ago

Hey just wanted to report that this little code adjustment works great:

Only downside is the script resumes on the NEXT query - therefore skipping the one that triggered the ban. I would do a code suggestion to change this but, again, I have no idea what I'm doing in the code dept. :-)