Summary of kayak.azal.az [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 5th, 2026 16:33 GMT+0
Server IP:151.101.137.29
Reverse DNS:-
Location:Montreal, Canada
Version:for desktop
Your final score:
- A
- B
- C
- F
A
Test Results Summary for kayak.azal.az
- 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.
- No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, Cookie Disclaimer. Show details.
- No obvious PCI DSS compliance issues were detected for Requirements 6.3 and 6.4. Show details.
- Issues were identified with key security headers: missing Strict-Transport-Security, X-Frame-Options; misconfigured Content-Security-Policy. Some optional HTTP headers may not be properly configured: Server, Content-Security-Policy-Report-Only, Report-To. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
- Content-Security-Policy is enforced but configuration issues were identified: directive errors, overly permissive directives, deprecated directives. The report-only Content-Security-Policy contains issues: directive errors, overly permissive directives, deprecated directives. Show details.
- 9 cookies detected; mst_ADIrkw, mst_iBfK2g, csid, mst_client have security or privacy-related configuration issues. Show details.
- 179 external requests detected; all requests completed successfully. SRI is not used for 178 third-party JavaScript and CSS files. Show details.
- No significant anti-scraping protections were detected. Show details.
Compliance Summary for kayak.azal.az
- 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 Passed: No obvious PCI DSS compliance issues were detected for Requirements 6.3 and 6.4.


