Summary of megamovil.mx [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Oct 31st, 2026 04:29 GMT+0
Server IP:34.225.58.161
Reverse DNS:ec2-34-225-58-161.compute-1.amazonaws.com
Location:Ashburn, United States
Version:for desktop
Your final score:
- A
- B
- C
- F
C
This test was made 9 days ago and may be outdated
Refresh Test
Test Results Summary for megamovil.mx
- 13 third-party web software dependancies were identified, including 13 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: bootstrap, jquery, modernizr, and others. Show details.
- Potential GDPR compliance issues were identified related to Privacy Policy, Website Security, 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 header misconfigured Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, Permissions-Policy, Referrer-Policy, Cache-Control. 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.
- 4 cookies detected; _ictid, _ga, _ga_7QTDRDWLMN, PHPSESSID have security or privacy-related configuration issues. Show details.
- 28 external requests detected; 1 request failed. SRI is implemented for 1 out of 22 third-party JavaScript and CSS files. Show details.
- No significant anti-scraping protections were detected. Show details.
- DNS A record detected; DNSSEC signatures are not present. Show details.
Compliance Summary for megamovil.mx
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Privacy Policy, Website Security, Cookie Disclaimer.
- PCI DSS Compliance Failed: Potential PCI DSS compliance issues were identified related to Requirements 6.3 and 6.4.