From 82153fb6e403f6f0ca2b5872e98ec0c38ad77e4a Mon Sep 17 00:00:00 2001 From: Thomas Date: Mon, 6 Nov 2017 11:54:35 -0600 Subject: [PATCH] Destroyed What to expect (markdown) --- What-to-expect.md | 15 --------------- 1 file changed, 15 deletions(-) delete mode 100644 What-to-expect.md diff --git a/What-to-expect.md b/What-to-expect.md deleted file mode 100644 index 164a71d..0000000 --- a/What-to-expect.md +++ /dev/null @@ -1,15 +0,0 @@ -# Expectations from Zeus - -*** - -Zeus can be expected to perform accurately and efficiently, you can also expect Zeus to not get requested a captcha and also not get IP banned from the search engines. Zeus uses a different approach to dork scanning then any other dork scanner out there. There are no search engine API calls and Zeus itself only calls the search engine once per session. - -# Errors that can be expected - -Zeus of course has errors just like everything else does. But most of these errors can be avoided if you use Zeus properly. - - - If you exit (CNTRL-C) before the automated web browser is done gathering the URL to search, this will result in an error. - - Youtube has tendency to cause nmap errors when performing a port scan on it - - Sqlmap errors will happen due to the API - -These errors are the most common, if you run across an error that is not mentioned here, you should make an [issue](https://github.com/Ekultek/Zeus-Scanner/issues). \ No newline at end of file