Website Security Test of
beta.habtoorpalace.com

Test Results Summary for beta.habtoorpalace.com

• Web Software Security Test
  One third-party web software dependancy was identified. It appears to be outdated, but no known vulnerabilities were detected. No Content Management System (CMS) was identified. One CMS component, JS-library or framework was identified: react. Show details.
• GDPR Compliance Test
  No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, 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 Strict-Transport-Security, Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, X-Powered-By, Referrer-Policy, Cache-Control, X-Permitted-Cross-Domain-Policies. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy headers are not present. Show details.
• Cookies Privacy and Security Test
  5 cookies detected; _gcl_au, _ga, _ga_0BZNHCES17, sessionExpiry, sessionId have security or privacy-related configuration issues. Show details.
• External Content Security Test
  16 external requests detected; 4 requests failed. SRI is not used for 7 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  No significant anti-scraping protections were detected. Show details.
• DNSSEC Configuration Test
  DNS A record detected; DNSSEC signatures are not present. Show details.

Compliance Summary for beta.habtoorpalace.com

• GDPR Compliance Passed: No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, Cookie Disclaimer.
• PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.