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: 5733ddf49ff49cd1aad03549731f8ab5017d17a797911b76e61a44659c51a024
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/jdf/image_settings/printers/{printerId}
GET /api/v1/jdf/job_settings
GET /jdf/image_settings/printers/{printerId}
GET /jdf/job_settings
POST /api/v1/jdf/get_jdf
POST /jdf/get_jdf
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Open service 40.118.101.67:443 ยท prismapreparego-jdf.tst.cppinter.net
2026-01-23 14:31
HTTP/1.1 302 Found Content-Length: 0 Connection: close Date: Fri, 23 Jan 2026 14:32:17 GMT Server: Microsoft-IIS/10.0 Location: /swagger Request-Context: appId=cid-v1:b066fb2d-7c0e-428c-b5c7-009b1db3ba24 X-Powered-By: ASP.NET