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: 5733ddf49ff49cd1f3d88d6000d671d3e7a85524e7a85524e7a85524e7a85524
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths: POST /v1/auth POST /v1/data-loader
Open service 13.69.68.4:443 ยท api-loader.qeedio.com
2026-01-23 15:20
HTTP/1.1 301 Moved Permanently Content-Length: 0 Connection: close Date: Fri, 23 Jan 2026 15:20:37 GMT Server: Kestrel Location: index.html Request-Context: appId=cid-v1:60803521-3260-47cc-bbe4-d2f33768c13e