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

bot@idyllum:~$ Please wait, the scan will start shortly

bot@idyllum:~$ Scanning: /100

bot@idyllum:~$ Latest scan is in long queue and may take a while

bot@idyllum:~$ Web Security Optimization (WSO) scan failed! Please try again

This site redirects to

Invalid domain!

Please log in or sign up for a free account to see this report in its entirety!

# Website security scan results for dogood4goodhealth.org

------------------

## At a glance

Site scanned: dogood4goodhealth.org
Risk level: LOW
WSO score: 98 / 100
Ranks: in top 3.5% of tested sites
Date of scan: Jan. 15, 2022, 7:08 a.m.
SSL Status: [!!] SSL Issues found. Traffic to site is not properly encrypted. Please address the issue immediately!
Total alerts: 2

## Verdict

Well that's a well-built website! This is almost as good as it gets. Feel free to send this report to the development team and congratulate them on their efforts! The Idyllum Labs team gives the webmaster all thumbs-up.

# Environment info

------------------

## Server

IP: 165.160.13.20
Location: United States

## Uncategorized

UncommonHeaders (x-oracle-dms-ecid,x-oracle-dms-rid)

# OWASP ZAP scan results

------------------

## Informative alerts

[OK] PASSED Charset Mismatch
[+]
[OK] PASSED Content-Type Header Empty
[+]
[!!] FAILED Content-Type Header Missing
[+]
What does this mean?

The Content-Type header was either missing or empty.

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

Ensure each page is setting the specific and appropriate content-type value for the content being delivered.

[OK] PASSED CSP: Notices
[+]
[OK] PASSED CSP Scanner: Notices
[+]
[OK] PASSED CSP Scanner: X-Content-Security-Policy
[+]
[OK] PASSED CSP Scanner: X-WebKit-CSP
[+]
[OK] PASSED CSP: X-Content-Security-Policy
[+]
[OK] PASSED CSP: X-WebKit-CSP
[+]
[OK] PASSED Information Disclosure - Sensitive Information in HTTP Referrer Header
[+]
[OK] PASSED Information Disclosure - Sensitive Information in URL
[+]
[OK] PASSED Information Disclosure - Suspicious Comments
[+]
[OK] PASSED Loosely Scoped Cookie
[+]
[OK] PASSED Split Viewstate in Use
[+]
[OK] PASSED Timestamp Disclosure - Unix
[+]
[OK] PASSED Username Hash Found
[+]
[OK] PASSED WSDL File Detection
[+]
[OK] PASSED WSDL File Passive Scanner
[+]

## Low risk vulnerabilities

[OK] PASSED Absence of Anti-CSRF Tokens
[+]
[OK] PASSED Application Error Disclosure
[+]
[OK] PASSED Cookie No HttpOnly Flag
[+]
[OK] PASSED Cookie Without SameSite Attribute
[+]
[OK] PASSED Cookie Without Secure Flag
[+]
[OK] PASSED Cross-Domain JavaScript Source File Inclusion
[+]
[OK] PASSED Incomplete or No Cache-control and Pragma HTTP Header Set
[+]
[OK] PASSED Information Disclosure - Debug Error Messages
[+]
[OK] PASSED Old Asp.Net Version in Use
[+]
[OK] PASSED Private IP Disclosure
[+]
[OK] PASSED Referer Exposes Session ID
[+]
[OK] PASSED Secure Pages Include Mixed Content
[+]
[OK] PASSED Server Leaks Information via "X-Powered-By" HTTP Response Header Field(s)
[+]
[OK] PASSED Web Browser XSS Protection Not Enabled
[+]
[OK] PASSED X-AspNet-Version Response Header
[+]
[!!] FAILED X-Content-Type-Options Header Missing
[+]
What does this mean?

The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.

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

Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.

[OK] PASSED X-Debug-Token Information Leak
[+]

## Medium risk vulnerabilities

[OK] PASSED Cross-Domain Misconfiguration
[+]
[OK] PASSED CSP Scanner: script-src unsafe-inline
[+]
[OK] PASSED CSP Scanner: style-src unsafe-inline
[+]
[OK] PASSED CSP Scanner: Wildcard Directive
[+]
[OK] PASSED CSP: script-src unsafe-inline
[+]
[OK] PASSED CSP: style-src unsafe-inline
[+]
[OK] PASSED CSP: Wildcard Directive
[+]
[OK] PASSED Emails Found in the Viewstate
[+]
[OK] PASSED HTTP Parameter Override
[+]
[OK] PASSED Insecure JSF ViewState
[+]
[OK] PASSED Multiple X-Frame-Options Header Entries
[+]
[OK] PASSED Potential IP Addresses Found in the Viewstate
[+]
[OK] PASSED Session ID in URL Rewrite
[+]
[OK] PASSED Vulnerable JS Library
[+]
[OK] PASSED Weak Authentication Method
[+]
[OK] PASSED X-Frame-Options Defined via META (Non-compliant with Spec)
[+]
[OK] PASSED X-Frame-Options Header Not Set
[+]
[OK] PASSED X-Frame-Options Setting Malformed
[+]

## High risk vulnerabilities

[OK] PASSED Viewstate without MAC Signature (Sure)
[+]
[OK] PASSED Viewstate without MAC Signature (Unsure)
[+]

Manual inspection results

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

Find this WSO report online:

# Idyllum Labs is on a mission

------------------

Is the code hosted at dogood4goodhealth.org 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 dogood4goodhealth.org 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.

It is important to understand that we don't gather business information. We analyze used technology and are not interested in

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!

# 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.

Want to scan and monitor multiple sites at once?

Create an account
Yes, generating security reports with Idyllum Labs is free!
(Just as all the best things in life..)