Website Security Test of
support.binah.ai

Test Results Summary for support.binah.ai

• Web Software Security Test
  5 third-party web software dependancies were identified. All appear to be outdated, but no known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: next.js, core-js, ua-parser-js, and others. Show details.
• GDPR Compliance Test
  No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, 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, X-Powered-By, Access-Control-Allow-Origin, Permissions-Policy, Referrer-Policy. 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
  3 cookies detected; devrev_plug_user_ref, NEXT_LOCALE, _dd_s have security or privacy-related configuration issues. Show details.
• External Content Security Test
  139 external requests detected; all requests completed successfully. SRI is not used for 87 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 support.binah.ai

• GDPR Compliance Passed: No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, Cookie Disclaimer.
• PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.