Website Security Test of
esmb2.cht.com.tw

Test Results Summary for esmb2.cht.com.tw

• Web Software Security Test
  2 third-party web software dependancies were identified, including 2 outdated dependancies. A total of 2 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: jquery-validation, jquery. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Website Security. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: Cookie Protection, Cookie Disclaimer. Show details.
• PCI DSS Compliance Test
  Potential PCI DSS compliance issues were identified related to Requirements 6.3 and 6.4. Show details.
• HTTP Headers Security Test
  Issues were identified with key security header misconfigured Content-Security-Policy. An optional HTTP header may not be properly configured: Server. 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
  One cookie detected; JSESSIONID has security or privacy-related configuration issues. Show details.
• External Content Security Test
  8 external requests detected; all requests completed successfully. SRI is not used for 5 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 esmb2.cht.com.tw

• GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Website Security. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: Cookie Protection, Cookie Disclaimer.
• PCI DSS Compliance Failed: Potential PCI DSS compliance issues were identified related to Requirements 6.3 and 6.4.