Summary of globe.okta.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Oct 31st, 2026 12:58 GMT+0
Server IP:75.2.87.65
Reverse DNS:a9fda6e8074f1dfbe.awsglobalaccelerator.com
Location:Mount Hope, 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 globe.okta.com
- 4 third-party web software dependancies were identified, including 3 outdated dependancies. A total of 3 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: handlebars.js, core-js, core-js, and others. Show details.
- Potential GDPR compliance issues were identified related to 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, Referrer-Policy, Cache-Control. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
- Content-Security-Policy is enforced but configuration issues were identified: overly permissive directives, directive errors. A report-only Content-Security-Policy is not present. Show details.
- 2 cookies detected; JSESSIONID have security or privacy-related configuration issues. Show details.
- 15 external requests detected; all requests completed successfully. SRI is implemented for 5 out of 7 third-party JavaScript and CSS files. Show details.
- 3 robots.txt rules and 3 bot protection mechanisms detected. No protection detected via User-Agent blocks or meta restrictions. Show details.
Compliance Summary for globe.okta.com
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Website Security, Cookie Disclaimer.
- PCI DSS Compliance Failed: Potential PCI DSS compliance issues were identified related to Requirements 6.3 and 6.4.