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 104.45.154.200:443 · qa-supplychainstructureservice.bentley.com
2026-01-12 08:19
HTTP/1.1 404 Not Found
Connection: close
Content-Type: application/problem+json; charset=utf-8
Date: Mon, 12 Jan 2026 08:20:08 GMT
Server: Microsoft-IIS/10.0
Cache-Control: no-cache, no-store, must-revalidate
Expires: 0
Pragma: no-cache
Transfer-Encoding: chunked
X-Correlation-ID: 400019d4-0000-0300-b63f-84710c7967bb
X-Powered-By: ASP.NET
{"type":"https://httpstatuses.io/404","title":"Not Found","status":404,"traceId":"00-a1da7419af1cfd5b738a7979e1c5af1b-0de0359fa1bddbc4-00"}
Open service 104.45.154.200:80 · qa-supplychainstructureservice.bentley.com
2026-01-12 08:19
HTTP/1.1 301 Moved Permanently Content-Length: 0 Connection: close Date: Mon, 12 Jan 2026 08:20:08 GMT Location: https://qa-supplychainstructureservice.bentley.com/