nginx 1.14.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: 5733ddf49ff49cd1bf890109bf890109bf890109bf890109bf890109bf890109
Public Swagger UI/API detected at path: /api-docs/swagger.json
Open service 3.216.42.100:443 ยท www.almightyninja.com
2026-01-23 02:40
HTTP/1.1 302 Found Server: nginx/1.14.0 (Ubuntu) Date: Fri, 23 Jan 2026 02:40:10 GMT Content-Type: text/plain; charset=utf-8 Content-Length: 29 Connection: close X-Powered-By: Express Access-Control-Allow-Origin: * Access-Control-Allow-Methods: GET, POST, OPTIONS, PUT, PATCH Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept Location: /v2/app Vary: Accept, Accept-Encoding Set-Cookie: connect.sid=s%3AlOHRY304_qhd2yI83QEhpWWL09Pz1VLb.blRi1b3gXHgmEGdfjVRtCmSIcbgn%2BoUroWqjRdw5Ja4; Path=/; HttpOnly Found. Redirecting to /v2/app