mirror of
https://github.com/Ekultek/Zeus-Scanner.git
synced 2026-03-11 08:55:51 +00:00
Destroyed What to expect (markdown)
parent
2954f03e1c
commit
82153fb6e4
1 changed files with 0 additions and 15 deletions
|
|
@ -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).
|
||||
Loading…
Reference in a new issue