Getting HTTP code 503 (google detects) after 3rd dork about pagodo

[opsdisk]

Hi @syriusbughunt - The defaults have worked for me in the past. Keep -l at 100, definitely randomize the user agent (don't use -u). It's a game of patience coming from 1 IP.

For the proxy, you could use proxychains. You provide a list of proxies, enable random_chain, and set chain_len = 1 to have it round robin through them. Here's what my /etc/proxychains4.conf file looks like. The two proxies are local SOCKS proxies.

random_chain
chain_len = 1
proxy_dns 
remote_dns_subnet 224
tcp_read_time_out 15000
tcp_connect_time_out 8000
[ProxyList]
socks4 	127.0.0.1 9050
socks4 	127.0.0.1 9051

Then just throw proxychains infront and you should be good:

proxychains python3 pagodo.py -g ALL_dorks.txt -s -e 35.0 -l 700 -j 1.1

I wrote a book on SSH tunneling, port redirection, and utilizing proxies if you want to learn more about it: https://cph.opsdisk.com

[opsdisk]

Actually, try with round_robin enabled instead of random_chain. In my testing, it switches proxies with each lookup.

[syriusbughunt]

May I suggest to add maybe an option '--proxy' that would load a list of VALID proxies or socks and throttle between them when they get error 503? It's kinda easy for me to say that but for the dev I don't know if this is hard to do... anyways if I can do some testing or anything, let me know!

[syriusbughunt]

Awesome solution! Will be definitely useful with also others applications, do you mind leaving this issue opened for a small time (just for the time I try it out) ?

Thanks !

[opsdisk]

Not at all, as long as you let me know what worked for you and any data you collected on speed/efficiencies (you were able to cut the delay down to 3 seconds with 5 servers, stuff like that). If it works well, I'll add it to the README.

[opsdisk]

@syriusbughunt Did that work for you?

[opsdisk]

#31