Website Security Test of
corescientific.com

Test Results Summary for corescientific.com

• Web Software Security Test
  10 third-party web software dependancies were identified, including 4 outdated dependancies. No known vulnerabilities were detected. 5 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, slick, 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 header misconfigured Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, Cache-Control. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy is enforced but configuration issues were identified: directive errors. A report-only Content-Security-Policy is not present. Show details.
• Cookies Privacy and Security Test
  4 cookies detected; _ga, _ga_E0YHRP1DS8, _rdt_uuid, _gcl_au have security or privacy-related configuration issues. Show details.
• External Content Security Test
  24 external requests detected; 6 requests failed. SRI is not used for 10 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  No significant anti-scraping protections were detected. Show details.
• DNSSEC Configuration Test
  DNS A record detected; DNSSEC signatures are not present. Show details.

Compliance Summary for corescientific.com

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