Summary of www.chathambarsinn.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 8th, 2026 08:01 GMT+0
Server IP:108.61.32.75
Reverse DNS:108.61.32.75.reliableservers.com
Location:Piscataway, United States
Version:for desktop
Your final score:
- A
- B
- C
- F
B-
Test Results Summary for www.chathambarsinn.com
- 2 third-party web software dependancies were identified. All appear to be outdated, but no known vulnerabilities were detected. One identified third-party web software dependancy has an unknown version. The identified CMS (ProcessWire Open Source CMS) appears to be outdated. One CMS component, JS-library or framework was identified: lit-html. Show details.
- Potential GDPR compliance issues were identified related to 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; misconfigured X-Frame-Options. Optional HTTP headers appear to be properly configured: Server, X-Powered-By. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
- Content-Security-Policy headers are not present. Show details.
- 15 cookies detected; sa_ftid.5022, osano_consentmanager_uuid, _ga_5CL567WM3N, _ga, _fbp, sa_ftses.5022, osano_consentmanager, _gcl_au, _ga_QFVGP7JR00, sa-user-id, sjrn_ccid, sa-user-id-v2, sa-user-id-v3, sa-user-id-v4 have security or privacy-related configuration issues. Show details.
- 121 external requests detected; 14 requests failed. SRI is not used for 50 third-party JavaScript and CSS files. Show details.
- 6 robots.txt rules and 5 bot protection mechanisms detected. No protection detected via User-Agent blocks or meta restrictions. Show details.
Compliance Summary for www.chathambarsinn.com
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Cookie Disclaimer.
- PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.