Website Security Test of
www.caremessage.org

Test Results Summary for www.caremessage.org

• Web Software Security Test
  16 third-party web software dependancies were identified, including 6 outdated dependancies. No known vulnerabilities were detected. 6 identified third-party web software dependancies have unknown versions. The CMS (WordPress) was identified, however, its version could not be determined. The following CMS components, JS-libraries or frameworks were identified: jquery, jquery-migrate, imagesloaded, and others. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Cookie Disclaimer. Show details.
• PCI DSS Compliance Test
  The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4. Show details.
• HTTP Headers Security Test
  Issues were identified with key security headers: missing Strict-Transport-Security, Content-Security-Policy, X-Frame-Options. Some optional HTTP headers may not be properly configured: Server, Permissions-Policy. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy headers are not present. Show details.
• Cookies Privacy and Security Test
  10 cookies detected; _ga_S7XJXXC37Z, _ga, wp_consent_marketing, wp_consent_functional, _gcl_au, wp_consent_statistics, wp_consent_preferences, cookieyes-consent, wp_consent_statistics-anonymous, _wpfuuid have security or privacy-related configuration issues. Show details.
• External Content Security Test
  22 external requests detected; 4 requests failed. SRI is not used for 7 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  No significant anti-scraping protections were detected. Show details.

Compliance Summary for www.caremessage.org

• GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Cookie Disclaimer.
• PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.