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: 5733ddf49ff49cd1aad035493b3b73504043c671384ca348384ca348384ca348
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET / GET /health GET /protos/voiceauth
Open service 13.69.68.4:443 ยท test.insight360.world
2026-01-23 15:06
HTTP/1.1 200 OK Connection: close Content-Type: text/plain; charset=utf-8 Date: Fri, 23 Jan 2026 15:06:40 GMT Server: Kestrel Transfer-Encoding: chunked Request-Context: appId=cid-v1:b79b2d31-a9a6-4bd4-8fe5-6f93546f14ac Communication with gRPC endpoints must be made through a gRPC client. To learn how to create a client, visit: https://go.microsoft.com/fwlink/?linkid=2086909