Website Security Test of
raydium.io

Test Results Summary for raydium.io

• Web Software Security Test
  5 third-party web software dependancies were identified, including 5 outdated dependancies. A total of 27 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: lodash, axios, next.js, and others. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Privacy Policy, Website Security, Cookie Disclaimer. Show details.
• PCI DSS Compliance Test
  The website is compliant with PCI DSS Requirement 6.4, while being non-compliant with Requirement 6.3. 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: Content-Security-Policy-Report-Only, Report-To. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy is not enforced; only a report-only policy was detected. The report-only Content-Security-Policy contains issues: overly permissive directives, directive errors, deprecated directives. Show details.
• Cookies Privacy and Security Test
  4 cookies detected; _ga_DR3V6FTKE3, _ga have security or privacy-related configuration issues. Show details.
• External Content Security Test
  22 external requests detected; 2 requests failed. SRI is implemented for 1 out of 3 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  No significant anti-scraping protections were detected. Additional anti-scraping protection appears to be provided by external infrastructure. Show details.

Compliance Summary for raydium.io

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