Website Security Test of
bfl.ai

Test Results Summary for bfl.ai

• Web Software Security Test
  2 third-party web software dependancies were identified, including one outdated dependancy. No known vulnerabilities were detected. One identified third-party web software dependancy has an unknown version. The CMS (WordPress) was identified, however, its version could not be determined. One CMS component, JS-library or framework was identified: react. 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 X-Frame-Options; misconfigured Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, X-Powered-By, Cache-Control. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy is enforced but configuration issues were identified: directive errors, overly permissive directives. A report-only Content-Security-Policy is not present. Show details.
• Cookies Privacy and Security Test
  7 cookies detected; ph_phc_S5D9NAXVC6BGl2PWlhihIW6IcKFYloe6zvUZW9SU1Bu_posthog, bfl_attribution, bfl_posthog_window_id, bfl_posthog_session_id, __ph_opt_in_out_phc_S5D9NAXVC6BGl2PWlhihIW6IcKFYloe6zvUZW9SU1Bu, cookieyes-consent have security or privacy-related configuration issues. Show details.
• External Content Security Test
  24 external requests detected; 1 request failed. SRI is not used for 4 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 bfl.ai

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