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.212.64.8:443 ยท uat-api.data.redex.eco
2026-01-23 14:13
HTTP/1.1 200 OK Connection: close Date: Fri, 23 Jan 2026 14:14:10 GMT Server: Microsoft-IIS/10.0 Set-Cookie: ARRAffinity=49c4982e36da2c7004b8bfd96c625567486f31bbf8a5b76a99b48281d085dbad;Path=/;HttpOnly;Secure;Domain=uat-api.data.redex.eco Set-Cookie: ARRAffinitySameSite=49c4982e36da2c7004b8bfd96c625567486f31bbf8a5b76a99b48281d085dbad;Path=/;HttpOnly;SameSite=None;Secure;Domain=uat-api.data.redex.eco Transfer-Encoding: chunked X-Powered-By: ASP.NET Data Service Running V1.80.5-overwrite-unissued-514