Summary of www.kraken.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 12:44 GMT+0
Server IP:104.16.14.28
Reverse DNS:-
Location:N/A
Version:for desktop
Your final score:
- A
- B
- C
- F
A
Test Results Summary for www.kraken.com
- 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.
- 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 header misconfigured Content-Security-Policy. An optional HTTP header may not be properly configured: Permissions-Policy. 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.
- 11 cookies detected; AF_SYNC, OptanonConsent, afUserId, first_session, ab_experiments, utm_parameters, landing_page, ab_uuid, facade-lang have security or privacy-related configuration issues. Show details.
- 32 external requests detected; all requests completed successfully. SRI is not used for 4 third-party JavaScript and CSS files. Show details.
- No significant anti-scraping protections were detected. Additional anti-scraping protection appears to be provided by external infrastructure. Show details.
Compliance Summary for www.kraken.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 Passed: No obvious PCI DSS compliance issues were detected for Requirements 6.3 and 6.4.


