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: 5733ddf49ff49cd1aad03549eacc59317f0af24650766ac3d5d05d9663f212c6
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/addressList GET /api/pageList GET /api/textList POST /api/productSearch POST /api/saveDevice POST /api/sendMessage
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: 5733ddf49ff49cd1aad03549eacc59317f0af24650766ac3d5d05d9663f212c6
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/addressList GET /api/pageList GET /api/textList POST /api/productSearch POST /api/saveDevice POST /api/sendMessage
Open service 195.142.1.194:443 · linde-prodoc-api.wdtajans.com
2026-01-23 11:35
HTTP/1.1 401 Unauthorized Transfer-Encoding: chunked Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Fri, 23 Jan 2026 11:36:01 GMT Connection: close API Key was not provided.