Kestrel
tcp/443
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Open service 20.105.216.41:443 · beta.api.clear-app.com
2026-01-08 20:35
HTTP/1.1 404 Not Found Content-Length: 0 Connection: close Date: Thu, 08 Jan 2026 20:36:34 GMT Server: Kestrel
Open service 20.105.216.41:443 · beta.api.clear-app.com
2026-01-03 14:18
HTTP/1.1 404 Not Found Content-Length: 0 Connection: close Date: Sat, 03 Jan 2026 14:18:28 GMT Server: Kestrel
Open service 20.105.216.41:80 · beta.api.clear-app.com
2026-01-03 14:18
HTTP/1.1 301 Moved Permanently Content-Length: 0 Connection: close Date: Sat, 03 Jan 2026 14:18:27 GMT Location: https://beta.api.clear-app.com/
Open service 20.105.216.41:443 · beta.api.clear-app.com
2026-01-01 23:07
HTTP/1.1 404 Not Found Content-Length: 0 Connection: close Date: Thu, 01 Jan 2026 23:07:00 GMT Server: Kestrel