Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google started blocking your requests but dorkscout will keep making requests #5

Open
pieterdekoning opened this issue Apr 12, 2023 · 1 comment

Comments

@pieterdekoning
Copy link

pieterdekoning commented Apr 12, 2023

I have tried multiple solutions, but after 1 successful scan, it gives me this error.

I tried running it with the inbuilt proxy only

I tried it with torsocks & proxychains & inbuild proxy:

sudo proxychains torsocks docker run --net host -v dorkscout_data:/dorkscout r4yan/dorkscout:1.0 scan -d="/dorkscout/Sensitive Online Shopping Info.dorkscout" -H="/dorkscout/a.html" -x socks5://127.0.0.1:9050
[proxychains] config file found: /etc/proxychains.conf
[proxychains] preloading /usr/lib/x86_64-linux-gnu/libproxychains.so.4
[proxychains] DLL init: proxychains-ng 4.16
[proxychains] DLL init: proxychains-ng 4.16
Started scanning with /dorkscout/Sensitive Online Shopping Info.dorkscout

I tried it with torsocks & proxychains:

sudo proxychains torsocks docker run --net host -v dorkscout_data:/dorkscout r4yan/dorkscout:1.0 scan -d="/dorkscout/Sensitive Online Shopping Info.dorkscout" -H="/dorkscout/a.html"
[proxychains] config file found: /etc/proxychains.conf
[proxychains] preloading /usr/lib/x86_64-linux-gnu/libproxychains.so.4
[proxychains] DLL init: proxychains-ng 4.16
[proxychains] DLL init: proxychains-ng 4.16
Started scanning with /dorkscout/Sensitive Online Shopping Info.dorkscout

I tried every possible solution I can find. Tried running it trough docker, or the other way, same results.

Can you please help out?

I love your tool <3

@R4yGM
Copy link
Owner

R4yGM commented Apr 12, 2023

hi can you show me which specific error it gives you?

it could be possible that google is seeing too many requests from a single tor exit relay and it flags the ip as if it is a bot
as shown here: https://support.torproject.org/tbb/tbb-44/

to avoid this you could try to make multiple instances of tor to get the most possible different ips from tor using a tool like this https://github.com/trimstray/multitor or maybe try to modify the configuration file "/etc/tor/torrc" or in "path/to/your/torbrowser/Data/Tor/torrc" to cycle proxies faster:

MaxCircuitDirtiness 10

10 are the seconds between a circuit and another, the default value is 10 minutes
the only issue is that you could still get the old ip of the exit relay and it is not uncommon to get it (https://stem.torproject.org/faq.html#how-do-i-request-a-new-identity-from-tor), so in both cases since the tor proxy is widely used you could get errors or not depends if you are lucky or not since there isn't a way to bypass google captcha

i have already used some of these techniques to get interesting scans and sometimes it worked others i had to retry multiple times since scraping google isn't easy at all.
anyways thank you :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants