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: 5733ddf49ff49cd1b6e67656b6e67656b6e67656b6e67656b6e67656b6e67656
Public Swagger UI/API detected at path: /swagger-ui.html
Open service 2.18.64.209:443 ยท customer.imastiapp.com
2026-01-23 03:49
HTTP/1.1 404 Not Found
Content-Type: application/json
Access-Control-Allow-Credentials: true
Access-Control-Allow-Methods: *
Access-Control-Allow-Headers: *
Access-Control-Max-Age: 3600
Vary: origin
Vary: access-control-request-method
Vary: access-control-request-headers
Expires: Fri, 23 Jan 2026 03:49:23 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 23 Jan 2026 03:49:23 GMT
Alt-Svc: h3=":443"; ma=93600,h3-29=":443"; ma=93600
Content-Length: 104
Connection: close
Server-Timing: cdn-cache; desc=MISS
Server-Timing: edge; dur=160
Server-Timing: origin; dur=4
Server-Timing: ak_p; desc="1769140162979_389797280_79435375_16303_581_0_12_-";dur=1
{"timestamp":1769140163079,"status":404,"error":"Not Found","message":"No message available","path":"/"}