Summary of www.mapfre.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 9th, 2026 09:52 GMT+0
Server IP:13.225.196.13
Reverse DNS:server-13-225-196-13.yul62.r.cloudfront.net
Location:Mount Hope, United States
Version:for desktop
Your final score:
- A
- B
- C
- F
C
Test Results Summary for www.mapfre.com
- 8 third-party web software dependancies were identified, including 6 outdated dependancies. One known vulnerability was detected. One identified third-party web software dependancy has an unknown version. The CMS (WordPress) was identified, however, its version could not be determined. The following CMS components, JS-libraries or frameworks were identified: moment, jquery, react, and others. Show details.
- Potential GDPR compliance issues were identified related to Website Security. 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. An optional HTTP header may not be properly configured: Access-Control-Allow-Origin. 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; OptanonConsent, wp-wpml_current_language have security or privacy-related configuration issues. Show details.
- 22 external requests detected; 1 request failed. SRI is not used for 9 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 www.mapfre.com
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Website Security.
- PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.4, while being non-compliant with Requirement 6.3.