ws.close.com operates as a WebSocket endpoint, which is a technical service rather than a visitor-friendly website. The HTTP 426 status you see is actually expected for WebSocket connections — it's not a malfunction. But what's missing here is the usual backbone of trust: there's no about page, no contact information, and no privacy policy or terms of service. For a protocol-level service, some of that absence is normal, but it also means you have no way to verify the operator or understand how data might be used. If you're integrating this endpoint into your own project, make sure your confidence comes from the parent domain (close.com) or from independent documentation — because this subdomain alone doesn't offer enough to evaluate. That's why our ws.close.com review ends with a 'use caution' verdict; there's no evidence of malicious intent, but there's also very little to go on.
In plain English
ws.close.com is a WebSocket server, not a standard website, which explains some unusual signals like the HTTP 426 status. But the total lack of contact info, legal pages, or any public identity makes it hard to assess who's behind it. If you're using this endpoint as part of an application, you should verify the parent domain and how your data is handled before trusting it fully.
Where the score comes from
Modern TLS with a valid certificate from a reputable issuer, plus fast page load. No security headers are set, but this is not unusual for a non-browser-facing endpoint.
As a subdomain, WHOIS records aren't available for this specific host. No about page, team info, or company disclosure means there's no way to know who operates this service.
Not on any blacklists and not flagged by Google Web Risk, which is good. But no web archive history and no Tranco ranking suggest the site is either very new or not widely used.
No contact information, about page, or social media presence. For a technical endpoint, this is common, but it leaves visitors without a way to reach the operator.
Missing privacy policy and terms of service. If this endpoint collects any user data, that gap matters. But the site appears to be a protocol server, not a data-collecting business.
Hosted on AWS with multiple IPs and fast response times. No email handling is expected for a WebSocket service. DNSSEC is absent but not critical here.
What we checked
Run this site? Show your score.
Add a trust badge so visitors can see your live score for themselves.
Get your badge →