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.206.176.5:443 ยท dev.core.pki.rest
2026-01-23 14:33
HTTP/1.1 200 OK Connection: close Content-Type: text/html Date: Fri, 23 Jan 2026 14:34:09 GMT Server: Kestrel Accept-Ranges: bytes Cache-Control: no-cache, no-store, must-revalidate ETag: "1dc7f12844d2828" Expires: -1 Last-Modified: Tue, 06 Jan 2026 13:44:02 GMT Transfer-Encoding: chunked