openresty
tcp/80
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 3.90.123.2:80 ยท link.livetula.com
2026-01-08 18:45
HTTP/1.1 404
Server: openresty
Date: Thu, 08 Jan 2026 18:45:57 GMT
Content-Type: application/json
Transfer-Encoding: chunked
Connection: close
Vary: origin,access-control-request-method,access-control-request-headers,accept-encoding
X-Frame-Options: DENY
Expires: 0
X-Content-Type-Options: nosniff
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
{
"timestamp" : "2026-01-08T18:45:57.894+00:00",
"status" : 404,
"error" : "Not Found",
"message" : "",
"path" : "/"
}