Summary of accident-health-claims.qbe.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 9th, 2026 10:37 GMT+0
Server IP:13.75.178.145
Reverse DNS:-
Location:Sydney, Australia
Version:for desktop
Your final score:
- A
- B
- C
- F
C
Test Results Summary for accident-health-claims.qbe.com
- 12 third-party web software dependancies were identified, including 10 outdated dependancies. A total of 14 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: lodash, moment, ua-parser-js, and others. Show details.
- 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.
- Potential PCI DSS compliance issues were identified related to Requirements 6.3 and 6.4. Show details.
- Issues were identified with key security headers: missing Strict-Transport-Security, Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, Cache-Control. Show details.
- Content-Security-Policy headers are not present. Show details.
- No cookies were detected. Show details.
- 19 external requests detected; all requests completed successfully. SRI is not used for 3 third-party JavaScript and CSS files. Show details.
- No significant anti-scraping protections were detected. Show details.
- DNS CNAME record detected; DNSSEC signatures are not present. Show details.
Compliance Summary for accident-health-claims.qbe.com
- 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.