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
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354906daf5d4b592093b032788e842939cdee1735798
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /categories
GET /categories/{categoryId}
GET /me
GET /partners
GET /partners/{partnerId}
GET /profiles
GET /profiles/{profileId}
POST /auth/token
POST /me/picture
Open service 20.206.176.5:443 ยท dev.api.admin.changeback.app
2026-01-23 05:10
HTTP/1.1 404 Not Found Content-Length: 0 Connection: close Date: Fri, 23 Jan 2026 05:10:55 GMT Server: Kestrel