bot@idyllum:~$ Please wait, the scan will start shortly
bot@idyllum:~$ Scanning: /100
bot@idyllum:~$ Web Security Optimization (WSO) scan failed! Please try again
This site redirects to
The source code of the tested site contains comments which may contain sensitive data. Like parts of code, url-s or program logic. This could give valuable hints to the potential attacker.
The source code of the tested site contains comments which may contain sensitive data. Like parts of code, url-s or program logic. This could give valuable hints to the potential attacker.What does this mean?
An attacker who finds these comments can map the application's structure and files, expose hidden parts of the site, and study the fragments of code to reverse engineer the application, which may help develop further attacks against the site.
The response appears to contain suspicious comments which may help an attacker.Where exactly is this vulnerability found?
We recommend inspecting your source code (even with your browser). Search for words like "BUG", "HACK", "FIXME", "LATER", "TODO" etc. The issues should be clearly visible.
Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.Real world example
Comments in code are not dangerous themselves. But if a comment gives an attacker hints about system architecture, SQL injections can soon follow. For Yahoo, this caused the loss of 450,000 login credentials back in 2012.
Ensure that the HttpOnly flag is set for all cookies.
Because of this your stored user preferences could leak to other websites and vice versa.
Because of this your stored user preferences could leak to other websites and vice versa.What does this mean?
Same-site cookies allow servers to mitigate the risk of CSRF and information leakage attacks by asserting that a particular cookie should only be sent with requests initiated from the same registrable domain.
A cookie has been set without the SameSite attribute, which means that the cookie can be sent as a result of a 'cross-site' request. The SameSite attribute is an effective counter measure to cross-site request forgery, cross-site script inclusion, and timing attacks.Where exactly is this vulnerability found?
Setting a Same-Site attribute to a cookie is quite simple. It consists of adding just one instruction to the cookie. Simply adding 'SameSite=Lax' or 'SameSite=Strict' is enough!
Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.
Because of this customers accessing your site from insecure or public networks can lose their login details.
Because of this customers accessing your site from insecure or public networks can lose their login details.What does this mean?
If your important site cookies are transmitted unencrypted, someone could steal them. By stealing an unencrypted session cookie an attacker could just log in as the user. This could easily happen in public WiFi networks.
A cookie has been set without the secure flag, which means that the cookie can be accessed via unencrypted connections.Where exactly is this vulnerability found?
Please add a “secure” flag to all cookies that contain sensitive information. This way you can protect yourself and your users from eavesdropping.
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.Real world example
Eavesdropping is the act of secretly or stealthily listening to the private conversation or communications of others without their consent. This type of network attack is generally one of the most effective ones.
Because of this your users on public computers could press the back button and view secure pages even after logging out.
Because of this your users on public computers could press the back button and view secure pages even after logging out.What does this mean?
The cache-control and pragma HTTP header have not been set properly or are missing allowing the browser and proxies to cache content.Where exactly is this vulnerability found?
"Please review how your system handles page caching. An software update might help too as many modern content management systems deal have eliminated the issue. If you need to configure this behaviour yourself then on Apache you can add the following directive to your .htaccess file: <IfModule mod_headers.c> Header set Cache-Control ""no-cache, no-store, must-revalidate"" Header set Pragma ""no-cache"" Header set Expires 0 </IfModule> However, please be aware that disabling caching all pages may have a negative impact on page responsiveness. On Debian based system, you can use the following command to make sure mod_headers is loaded: sudo a2enmod headers After enabling the module, you need to restart your server sudo service apache restart Alernatively you may control the Cache-Control headers from your application source code. For instance in php you can set it using the header(); function"
Whenever possible ensure the cache-control HTTP header is set with no-cache, no-store, must-revalidate; and that the pragma HTTP header is set with no-cache.
The web/application server is leaking information via one or more 'X-Powered-By' HTTP response headers. Access to such information may facilitate attackers identifying other frameworks/components your web application is reliant upon and the vulnerabilities such components may be subject to.Where exactly is this vulnerability found?
Ensure that your web server, application server, load balancer, etc. is configured to suppress 'X-Powered-By' headers.
Because of this some essential parts of the sites code come from third-parties and are therefore not fully under the administrators control. If these sources get hacked or change their behavior you and your customers are at risk.
Because of this some essential parts of the sites code come from third-parties and are therefore not fully under the administrators control. If these sources get hacked or change their behavior you and your customers are at risk.What does this mean?
For example, your third-party code provider may suddenly decide they want to collect data from end-users of their script, and this data might include cookies, and HTML5 storage data. By including the script on their domain you are allowing them to make these changes without agreement from you.
The page includes one or more script files from a third-party domain.Where exactly is this vulnerability found?
Downloading the code and hosting from your own domain is the safe approach.
This site has not been manually inspected yet. Please apply for an inspection here
Is www.faketaxi.com secure and safe to use?
We at Idyllum Labs wanted to find out! That is why we built this automated website security scanner and generated this report.
Please understand, that is an automated and unbiased OWASP ZAP based website security scan for www.faketaxi.com and has nothing to do with human subjectivity, thoughts, opinions or relationships.
If you have comments, don't agree with the results or want to submit a site for manual examination, don't hesitate to contact us.
Run a free OWASP ZAP scan for any website at Idyllum.com!
Want to scan and monitor multiple sites at once?Create an account