Summary of events.nokia.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Oct 5th, 2026 20:02 GMT+0
Server IP:100.63.194.47
Reverse DNS:ec2-100-63-194-47.compute-1.amazonaws.com
Location:Ashburn, United States
Version:for desktop
Your final score:
- A
- B
- C
- F
C
This test was made 34 days ago and may be outdated
Refresh Test
Test Results Summary for events.nokia.com
- 2 third-party web software dependancies were identified. One dependancy is outdated and has one known vulnerability. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: jquery-cookie, jquery. Show details.
- Potential GDPR compliance issues were identified related to Website Security. 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, Access-Control-Allow-Origin, Cache-Control. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
- Content-Security-Policy is enforced but configuration issues were identified: directive errors. A report-only Content-Security-Policy is not present. Show details.
- 4 cookies detected; _gat_UA-125559045-1, _gid, _ga, PHPSESSID have security or privacy-related configuration issues. Show details.
- 15 external requests detected; all requests completed successfully. SRI is not used for 11 third-party JavaScript and CSS files. Show details.
- 7 User-Agent blocks and 6 bot protection mechanisms detected. No protection detected via robots.txt rules or meta restrictions. Show details.
- DNS CNAME record detected; DNSSEC signatures are not present. Show details.
Compliance Summary for events.nokia.com
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Website Security.
- PCI DSS Compliance Failed: Potential PCI DSS compliance issues were identified related to Requirements 6.3 and 6.4.