Summary of hospital.latica.ai [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 7th, 2026 15:16 GMT+0
Server IP:13.225.196.31
Reverse DNS:server-13-225-196-31.yul62.r.cloudfront.net
Location:Mount Hope, United States
Version:for desktop
Your final score:
- A
- B
- C
- F
C
Test Results Summary for hospital.latica.ai
- 7 third-party web software dependancies were identified, including 6 outdated dependancies. A total of 3 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: lodash, bootstrap, core-js, and others. Show details.
- Potential GDPR compliance issues were identified related to Privacy Policy, Website Security, Cookie Disclaimer. Show details.
- Potential PCI DSS compliance issues were identified related to Requirements 6.3 and 6.4. Show details.
- Issues were identified with key security header misconfigured Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, Referrer-Policy. 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.
- One cookie detected; mp_866a9a5765418ea030be71e6e265786b_mixpanel has security or privacy-related configuration issues. Show details.
- 4 external requests detected; all requests completed successfully. SRI is implemented for 2 out of 4 third-party JavaScript and CSS files. Show details.
- No significant anti-scraping protections were detected. Show details.
- 4 DNS A records detected; DNSSEC signatures are not present. Show details.
Compliance Summary for hospital.latica.ai
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Privacy Policy, Website Security, Cookie Disclaimer.
- PCI DSS Compliance Failed: Potential PCI DSS compliance issues were identified related to Requirements 6.3 and 6.4.