Website Security Test of
corporate.zalando.de

Test Results Summary for corporate.zalando.de

• Web Software Security Test
  5 third-party web software dependancies were identified, including 3 outdated dependancies. No known vulnerabilities were detected. One identified third-party web software dependancy has an unknown version. The CMS (Drupal) was identified, however, its version could not be determined. The following CMS components, JS-libraries or frameworks were identified: jquery-ui, modernizr, bootstrap, 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 headers: missing Strict-Transport-Security, Content-Security-Policy. Optional HTTP header appears to be properly configured: Cache-Control. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy headers are not present. Show details.
• Cookies Privacy and Security Test
  3 cookies detected; _gid, _gat_zalga, _ga have security or privacy-related configuration issues. Show details.
• External Content Security Test
  21 external requests detected; all requests completed successfully. SRI is not used for 3 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  No significant anti-scraping protections were detected. Show details.
• DNSSEC Configuration Test
  3 DNS A records detected; DNSSEC signatures are not present. Show details.

Compliance Summary for corporate.zalando.de

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