Website Security Test of
arnika-web.com

Test Results Summary for arnika-web.com

• Web Software Security Test
  7 third-party web software dependancies were identified, including 2 outdated dependancies. No known vulnerabilities were detected. 4 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, Popups for Divi, 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 missing Content-Security-Policy. Some optional HTTP headers may not be properly configured: Server, Content-Security-Policy-Report-Only, Permissions-Policy. 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: directive errors, overly permissive directives. Show details.
• Cookies Privacy and Security Test
  One cookie detected; _lscache_vary has security or privacy-related configuration issues. Show details.
• External Content Security Test
  2 external requests detected; all requests completed successfully. SRI is not used for one third-party JavaScript or CSS file. 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 arnika-web.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.