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: 5733ddf49ff49cd1aad0354906e5219d06e5219d06e5219d06e5219d06e5219d
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/status
Open service 23.36.162.13:443 ยท webhook.uipath.philips.com
2026-01-23 16:09
HTTP/1.1 404 Not Found Content-Length: 0 Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Fri, 23 Jan 2026 16:09:46 GMT Connection: close Strict-Transport-Security: max-age=31536000