Summary of idwebhost-236-52.ethz.ch [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 3rd, 2026 19:06 GMT+0
Server IP:129.132.236.52
Reverse DNS:idwebhost-236-52.ethz.ch
Location:Zurich, Switzerland
Version:for desktop
Your final score:
- A
- B
- C
- F
C
The website has at least one folder with enabled directory listing, putting its content at risk.
Misconfiguration or weakness
Test Results Summary for idwebhost-236-52.ethz.ch
- The CMS (YOURLS) was identified, however, its version could not be determined. No CMS components, JS-libraries or frameworks were identified. Show details.
- Potential GDPR compliance issues were identified related to Privacy Policy. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: Cookie Protection, Cookie Disclaimer. Show details.
- The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4. Show details.
- Issues were identified with key security headers: missing Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options. Optional HTTP header appears to be properly configured: Server. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
- Content-Security-Policy headers are not present. Show details.
- No cookies were detected. Show details.
- 2 external requests detected; all requests completed successfully. SRI is not used for one third-party JavaScript or CSS file. Show details.
- No significant anti-scraping protections were detected. Show details.
Compliance Summary for idwebhost-236-52.ethz.ch
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Privacy Policy. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: 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.