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.50.2.65:443 · dev.apps.bitcentral.rest
2026-01-23 13:58
HTTP/1.1 200 OK Content-Length: 0 Connection: close Date: Fri, 23 Jan 2026 13:58:47 GMT Server: Kestrel Request-Context: appId=cid-v1:6c8912d7-a774-4628-96dc-4913c9729974
Open service 20.50.2.65:443 · dev.apps.bitcentral.rest
2026-01-10 13:45
HTTP/1.1 200 OK Content-Length: 0 Connection: close Date: Sat, 10 Jan 2026 13:46:52 GMT Server: Kestrel Request-Context: appId=cid-v1:6c8912d7-a774-4628-96dc-4913c9729974
Open service 20.50.2.65:80 · dev.apps.bitcentral.rest
2026-01-10 13:45
HTTP/1.1 301 Moved Permanently Content-Length: 0 Connection: close Date: Sat, 10 Jan 2026 13:46:51 GMT Location: https://dev.apps.bitcentral.rest/