Website Vulnerability Scanner
The Website Vulnerability Scanner is a custom tool written by our team in order to quickly assess the security of a web application. It is a full-blown web application scanner, capable of performing comprehensive security assessments against any type of web application.
The free scan you can perform on this page is a Light Scan, while only paying customers have access to the Full Scan option. Here is the complete list of tests performed by this vulnerability scanner and the difference between Light and Full scans.
List of tests performed
|Light Scan||Full Scan||Tests performed|
|Fingerprint web server software|
|Analyze HTTP headers for security misconfiguration|
|Check the security of HTTP cookies|
|Check the SSL certificate of the server|
|Check if the server software is affected by known vulnerabilities|
|Analyze robots.txt for interesting URLs|
|Check whether a client access file exists, and if it contains a wildcard entry (clientaccesspolicy.xml, crossdomain.xml)|
|Discover server configuration problems such as Directory Listing|
|Check if HTTP TRACK/TRACE methods are enabled|
|Check for SQL Injection|
|Check for Cross-Site Scripting|
|Check for Local File Inclusion and Remote File Inclusion|
|Check for OS Command Injection|
|Check for ASP Cookieless Cross-Site Scripting|
|Check for Server Side Request Forgery|
|Check for Open Redirect|
|Check for PHP Code Injection|
|Find administrative pages|
|Check for sensitive files (archives, backups, certificates, key stores) based on hostname and some common words|
|Attempt to find interesting files / functionality|
|Check for information disclosure issues|
|Weak Password Submission Method|
|Clear Text Submission of Credentials|
|Verify Domain Sources|
|Check for commented code/debug messages|
|Find Login Interfaces|
|Sensitive Data Crawl|
|Target URL||This is the URL of the website that will be scanned. The tool does not follow any redirects, so the exact URL will be scanned. If you want to scan only a certain directory or path, you can add it in the URL like: |
|Light Scan||This is a fast, passive and non-intrusive scan.|
|Full Scan||This is a complete assessment which covers a much broader range of security tests.|
|Authentication - User/Password||The credentials for the scanner to try authentication before starting the scan.|
|Authentication - Cookie||A valid session cookie that will be used by the scanner to do authenticated scans.|
|Authentication - Headers||Custom HTTP headers that can also be used for authentication (ex. JWT tokens, Basic Authentication etc.)|
How it works
The Full version of the scanner includes all the tests from the Light scan and adds more complex security tests. It first crawls the target application then it sends various inputs into the parameters of the pages and looks for specific web vulnerabilities such as: SQL Injection, Cross-Site Scripting, Local File Inclusion, OS Command Injection and many more. Furthermore, the scanner also attempts to detect sensitive files from the server like backup files, old files, admin interfaces, archive files, etc.
While the Light Scan is passive and generates a maximum of 20 HTTP requests to the server, the Full Scan is more aggressive and it sends up to 10,000 HTTP requests. This may trigger alarms from IDS devices but you should know that it is not a destructive scan.
Since the Full Scan does a comprehensive website assessment, it can take up to several hours to complete. To keep your workflow uninterrupted, enable notifications that inform you when the web app scan has finished.
The Website Vulnerability Scanner is able to scan the target web application as an authenticated user. You can configure authentication in several ways:
- User/Password Authentication: When this option is chosen, the scanner will first try to authenticate to the provided login URL and obtain a valid session cookie. This cookie will be used with all the HTTP requests done to the server, performing an authenticated scan. You have the option to check if the authentication was successful before actually starting the scan.
- Cookie Authentication: With this option you can specify an already valid session cookie (or multiple cookies) that will be sent with each HTTP request to the server. You have to first get the session cookie by manually logging into your target application with a web browser and transferring the cookie from the browser to the scanner (copy/paste).
- Headers Authentication: This option allows you to specify custom HTTP headers that will be sent with each request to the target application. These can be used for authentication (e.g. JWT tokens, Basic Authentication, etc.) or for other specific application functionality.
- Recorded Authentication: This method gives you the possibility to record the steps required to authenticate into the target. The scanner will use this recording by replaying the actions and obtain a valid session every time it detects logging in again is required.