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: 5733ddf49ff49cd1aad0354984a2afca35cac17997d067843e387c843e387c84
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: POST /Account/Logout POST /Account/Manage/DownloadPersonalData POST /Account/Manage/LinkExternalLogin POST /Account/PerformExternalLogin
Open service 195.201.132.28:443 ยท protoxide.pau.dotfinity.eu
2026-01-23 09:17
HTTP/1.1 302 Found Alt-Svc: h3=":443"; ma=2592000 Content-Length: 0 Date: Fri, 23 Jan 2026 09:17:58 GMT Location: http://protoxide.pau.dotfinity.eu/Account/Login?ReturnUrl=%2F Server: Caddy Server: Kestrel Connection: close