Summary of www.mon-compte.bouyguestelecom.fr [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 9th, 2026 15:52 GMT+0
Server IP:184.25.128.131
Reverse DNS:a184-25-128-131.deploy.static.akamaitechnologies.com
Location:Montreal, Canada
Version:for desktop
Your final score:
- A
- B
- C
- F
C
Test Results Summary for www.mon-compte.bouyguestelecom.fr
- 11 third-party web software dependancies were identified, including 10 outdated dependancies. A total of 6 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: jquery, jquery-validation, backbone, 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 headers: missing X-Frame-Options; misconfigured Content-Security-Policy. Optional HTTP header appears to be properly configured: Cache-Control. 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; NoCookieVu, deployment_group have security or privacy-related configuration issues. Show details.
- 10 external requests detected; all requests completed successfully. SRI is not used for one third-party JavaScript or CSS file. 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.mon-compte.bouyguestelecom.fr
- 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.