Summary of utreder.investigate-t.insurance.storebrand.no [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 9th, 2026 10:52 GMT+0
Server IP:51.105.170.97
Reverse DNS:-
Location:Amsterdam, The Netherlands
Version:for desktop
Your final score:
- A
- B
- C
- F
C
Test Results Summary for utreder.investigate-t.insurance.storebrand.no
- 7 third-party web software dependancies were identified, including 6 outdated dependancies. A total of 11 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: dompurify, moment, highcharts, and others. Show details.
- Potential GDPR compliance issues were identified related to Privacy Policy, 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: Permissions-Policy, Referrer-Policy, Cache-Control, X-Permitted-Cross-Domain-Policies. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
- Content-Security-Policy is enforced but configuration issues were identified: overly permissive directives, directive errors. A report-only Content-Security-Policy is not present. Show details.
- 2 cookies detected; ApplicationGatewayAffinity, ApplicationGatewayAffinityCORS have security or privacy-related configuration issues. Show details.
- No external requests were detected. Show details.
- 3 User-Agent blocks and 2 bot protection mechanisms detected. No protection detected via robots.txt rules or meta restrictions. Show details.
Compliance Summary for utreder.investigate-t.insurance.storebrand.no
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Privacy Policy, 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.