Summary of www.royalenfield.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 5th, 2026 22:19 GMT+0
Server IP:23.60.176.165
Reverse DNS:a23-60-176-165.deploy.static.akamaitechnologies.com
Location:Toronto, Canada
Version:for desktop
Your final score:
- A
- B
- C
- F
C
Test Results Summary for www.royalenfield.com
- 13 third-party web software dependancies were identified, including 12 outdated dependancies. A total of 16 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: jquery-ui, bootstrap, handlebars.js, 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: misconfigured Content-Security-Policy, X-Frame-Options. Optional HTTP headers appear to be properly configured: Server, Cache-Control. 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.
- 18 cookies detected; _clsk, _clck, _sfid_efe4, _tt_enable_cookie, _evga_f1c1, _gcl_au, _ttp, _gid, _gat_UA-38397465-3, _gat_UA-38397465-14, ttcsid, _fbp, RT, _ga_7746PERT32, ttcsid_CNOTKPRC77UDD0LI1GSG, _ga have security or privacy-related configuration issues. Show details.
- 52 external requests detected; 6 requests failed. SRI is not used for 30 third-party JavaScript and CSS files. Show details.
- 12 User-Agent blocks and 8 bot protection mechanisms detected. No protection detected via robots.txt rules or meta restrictions. Show details.
- DNS CNAME record detected; DNSSEC signatures are not present. Show details.
Compliance Summary for www.royalenfield.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.
