From 24fa18e6bbd824cbe4c8f8a79f0c870a70d68c56 Mon Sep 17 00:00:00 2001 From: Thomas Perkins Date: Thu, 7 Sep 2017 14:47:16 -0500 Subject: [PATCH] Updated What to expect (markdown) --- What-to-expect.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/What-to-expect.md b/What-to-expect.md index a5e3815..164a71d 100644 --- a/What-to-expect.md +++ b/What-to-expect.md @@ -1 +1,15 @@ -Expectations from Zeus \ No newline at end of file +# 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