Website Security Test of
lovable.dev

Test Results Summary for lovable.dev

• Web Software Security Test
  One third-party web software dependancy was identified. It appears to be outdated, but no known vulnerabilities were detected. No Content Management System (CMS) was identified. One CMS component, JS-library or framework was identified: react. 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, Referrer-Policy, Cache-Control, Reporting-Endpoints, Cross-Origin-Opener-Policy-Report-Only. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy is enforced and appears to be properly configured. A report-only Content-Security-Policy is not present. Show details.
• Cookies Privacy and Security Test
  8 cookies detected; __cuid, rs_visitor_id, __dpl, LOCALE, USER_CURRENCY, USER_COUNTRY have security or privacy-related configuration issues. Show details.
• External Content Security Test
  3 external requests detected; all requests completed successfully. Show details.
• Protection from Data Scraping Test
  6 robots.txt rules and 5 bot protection mechanisms detected. No protection detected via User-Agent blocks or meta restrictions. Additional anti-scraping protection appears to be provided by external infrastructure. Show details.

Compliance Summary for lovable.dev

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