Summary of www.cpic.com.cn [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 9th, 2026 08:32 GMT+0
Server IP:220.196.85.123
Reverse DNS:-
Location:China
Version:for desktop
Your final score:
- A
- B
- C
- F
C
Test Results Summary for www.cpic.com.cn
- 3 third-party web software dependancies were identified, including 3 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, sa-sdk-javascript. Show details.
- Potential GDPR compliance issues were identified related to Website Security, Cookie Disclaimer. Show details.
- The website is compliant with PCI DSS Requirement 6.4, while being non-compliant with Requirement 6.3. Show details.
- Issues were identified with key security header misconfigured Content-Security-Policy. Optional HTTP headers appear to be properly configured: Referrer-Policy, X-Permitted-Cross-Domain-Policies. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
- 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.
- 8 cookies detected; puri, _apm_session, ppageid, sensorsdata2015jssdkcross, sajssdk_2015_cross_new_user, cms_appXF, pdomain, 122_vq have security or privacy-related configuration issues. Show details.
- 33 external requests detected; 5 requests failed. SRI is not used for 10 third-party JavaScript and CSS files. Show details.
- No significant anti-scraping protections were detected. Show details.
- 2 DNS A records detected; DNSSEC signatures are not present. Show details.
Compliance Summary for www.cpic.com.cn
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Website Security, Cookie Disclaimer.
- PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.4, while being non-compliant with Requirement 6.3.