sherlock-project
Reduce false positives (those caused by WAFs and bot detection)
Discussions are taking place elsewhere about false positives and bot detection circumvention.
The Cloudflare bypass, even if implemented, will fail occasionally as Cloudflare updates their detection methods. Until the maintainer of whatever bypass mechanism is able to update their tool, Sherlock users will randomly see false positives.
In either case, this PR significantly reduces the number of false positives that appear as more and more sites switch to using WAFs that function like Cloudflare. If a known WAF block page is detected, the QueryStatus of WAF is applied rather than running the standard (and now useless) error checks. Results with the status of WAF are only displayed with --print-all and bear a status message indicating such.
The error message also indicates that a proxy (such as FlareSolverr) may help.
[-] Myspace: Not Found!
[-] NICommunityForum: Not Found!
[-] NationStates Nation: Blocked by bot detection (proxy may help)
[-] NationStates Region: Blocked by bot detection (proxy may help)
[-] Naver: Not Found!
[-] Needrom: Not Found!
Paired with #2068, the number of false positives presented to the user drop significantly.
Fixes #1878 (as the use of a proxy may allow Fiverr to function as desired, and it won't display false positives otherwise)
Update: This PR now also includes a fingerprint for PerimeterX -- the "press and hold" captcha service sometimes also used by sites like Fiverr
