Website Security Test of
v2.auth.mistral.ai

Test Results Summary for v2.auth.mistral.ai

• Web Software Security Test
  2 third-party web software dependancies were identified. All appear to be outdated, but no known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: core-js, react. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Cookie Disclaimer. Show details.
• PCI DSS Compliance Test
  The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4. Show details.
• HTTP Headers Security Test
  Issues were identified with key security headers: missing X-Frame-Options; misconfigured Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, X-Powered-By, Cache-Control. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy is enforced but configuration issues were identified: overly permissive directives, directive errors, deprecated directives. A report-only Content-Security-Policy is not present. Show details.
• Cookies Privacy and Security Test
  All 3 detected cookies appear to be properly configured from a security perspective. Show details.
• External Content Security Test
  3 external requests detected; all requests completed successfully. SRI is correctly implemented for one third-party JavaScript or CSS file. Show details.
• Protection from Data Scraping Test
  No significant anti-scraping protections were detected. Additional anti-scraping protection appears to be provided by external infrastructure. Show details.
• DNSSEC Configuration Test
  2 DNS A records detected; DNSSEC signatures are not present. Show details.

Compliance Summary for v2.auth.mistral.ai

• GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Cookie Disclaimer.
• PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.