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 40.76.5.137:443 ยท demo-everifyapi.onblick.com
2026-01-23 03:42
HTTP/1.1 302 Found Content-Length: 0 Connection: close Content-Type: text/html Date: Fri, 23 Jan 2026 03:43:18 GMT Server: Microsoft-IIS/10.0 Cache-Control: private Location: /swagger Set-Cookie: ARRAffinity=e973e37452cb85d28c41dd081c9c63168050b12428ef8ac3da755ef395a95876;Path=/;HttpOnly;Secure;Domain=demo-everifyapi.onblick.com Set-Cookie: ARRAffinitySameSite=e973e37452cb85d28c41dd081c9c63168050b12428ef8ac3da755ef395a95876;Path=/;HttpOnly;SameSite=None;Secure;Domain=demo-everifyapi.onblick.com Strict-Transport-Security: max-age=2592000 Request-Context: appId=cid-v1:f14f7922-492f-4b94-8feb-6ee0ad3ef03b X-Powered-By: ASP.NET