Is secure and safe to use? | Web Security Optimization (WSO) report by Idyllum Labs.

Website security scan results for

Safe mode. Please [ log in ] to see the full report!

At a glance

Site scanned:
Date of scan: Oct. 2, 2021, 10:53 a.m.

Risk level: HIGH
Ranks: worse than 51.1% of tested sites
SSL Status: [OK] SSL Encryption enforced

Total OWASP ZAP alerts: 105
Nmap open ports found: 2


Location: Unknown
Web server: Sucuri/Cloudproxy

Open ports for (Nmap scan)

Port 80 (tcp) - http
Port 443 (tcp) - https

OWASP ZAP scan results


Informative alerts

Low risk vulnerabilities

What does this mean?

No Anti-CSRF tokens were found in a HTML submission form.A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.CSRF attacks are effective in a number of situations, including: * The victim has an active session on the target site. * The victim is authenticated via HTTP auth on the target site. * The victim is on the same local network as the target site.CSRF has primarily been used to perform an action against a target site using the victim's privileges, but recent techniques have been discovered to disclose information by gaining access to the response. The risk of information disclosure is dramatically increased when the target site is vulnerable to XSS, because XSS can be used as a platform for CSRF, allowing the attack to operate within the bounds of the same-origin policy.

Where exactly is this vulnerability found?
How to solve this?

Phase: Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.For example, use anti-CSRF packages such as the OWASP CSRFGuard.Phase: ImplementationEnsure that your application is free of cross-site scripting issues, because most CSRF defenses can be bypassed using attacker-controlled script.Phase: Architecture and DesignGenerate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).Note that this can be bypassed using XSS.Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.Note that this can be bypassed using XSS.Use the ESAPI Session Management control.This control includes a component for CSRF.Do not use the GET method for any request that triggers a state change.Phase: ImplementationCheck the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.

What does this mean?

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?
How to solve this?

Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.

What does this mean?

The response appeared to contain common error messages returned by platforms such as ASP.NET, and Web-servers such as IIS and Apache. You can configure the list of common debug messages.

Where exactly is this vulnerability found?
How to solve this?

Disable debugging messages before pushing to production.

What does this mean?

The page includes mixed content, that is content accessed via HTTP instead of HTTPS.

Where exactly is this vulnerability found?
How to solve this?

A page that is available over SSL/TLS must be comprised completely of content which is transmitted over SSL/TLS.The page must not contain any content that is transmitted over unencrypted HTTP. This includes content from third party sites.

Medium risk vulnerabilities

What does this mean?

The following directives either allow wildcard sources (or ancestors), are not defined, or are overly broadly defined: script-src, script-src-elem, script-src-attr, style-src, style-src-elem, style-src-attr, img-src, connect-src, frame-src, frame-ancestors, font-src, media-src, object-src, manifest-src, worker-src, prefetch-src, form-actionThe directive(s): frame-ancestors, form-action are among the directives that do not fallback to default-src, missing/excluding them is the same as allowing anything.

Where exactly is this vulnerability found?
How to solve this?

Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.

High risk vulnerabilities

Manual inspection results

This site has not been manually inspected yet. Please apply for an inspection here

Find this WSO report online:

Environment info







Title (SnapTrac - Kundel - Production Safety Systems)
Email ([''])
X-XSS-Protection (1; mode=block)
Content-Language (en)
MetaGenerator (['Drupal 7 ('])
[ 2 more ]
See hacks, ports, leaked data and possible attack routes for

Idyllum Labs is on a mission


Is the code hosted at vulnerable to cybersecurity attacks? Are the used systems up to date and respecting the security standards of 2022?

We at Idyllum Labs wanted to find out! That is why we built this automated website security scanner and generated this report.

Please note

This is an automated and unbiased website vulnerability scan for the domain and has nothing to do with human subjectivity, thoughts, opinions, or relationships.

Our cloud-based infrastructure crawls the internet using a mixture of OWASP ZAP, Nmap, Whatweb, and other great software to detect website security issues. We display this data for educational purposes - to give security guidelines for anyone interested in building a safer web environment.

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!

What next?


Dig deeper

  1. Log in or create a free account to gain access to this report in its entirety.
  2. Use our dashboard to automate security testing and set up automatic monitoring for your website portfolio.
  3. Scan a new domain or initiate a rescan for this domain.

Join our ranks

  1. Use these insights to build your systems bullet-proof.
  2. Explore our datasets and compare your results.
  3. Drop us a line! Help us expand our code or cloud or just say hi!
  4. Support the cause - your donation helps to keep this service free and unbiased.