Microsoft-IIS 10.0
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.118.48.5:443 ยท api.letsfit.uy
2026-01-23 12:20
HTTP/1.1 404 Not Found Content-Length: 0 Connection: close Date: Fri, 23 Jan 2026 12:21:24 GMT Server: Microsoft-IIS/10.0 Set-Cookie: ARRAffinity=a1e606c837b71de3bcdf8a18e601752e5807aa08d2deebcc598e5b0e5ad0959c;Path=/;HttpOnly;Secure;Domain=api.letsfit.uy Set-Cookie: ARRAffinitySameSite=a1e606c837b71de3bcdf8a18e601752e5807aa08d2deebcc598e5b0e5ad0959c;Path=/;HttpOnly;SameSite=None;Secure;Domain=api.letsfit.uy X-Powered-By: ASP.NET