nginx
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: 5733ddf49ff49cd110a331ec9ff6b0339ff6b0339ff6b0339ff6b0339ff6b033
Public Swagger UI/API detected at path: /v2/api-docs - sample paths: GET /error
Open service 13.210.246.142:443 ยท trxpay.hipayx.com
2026-01-23 16:04
HTTP/1.1 404
Server: nginx
Date: Fri, 23 Jan 2026 16:04:13 GMT
Content-Type: application/json
Transfer-Encoding: chunked
Connection: close
Vary: Origin
Vary: Access-Control-Request-Method
Vary: Access-Control-Request-Headers
{"timestamp":"2026-01-23T16:04:13.250+00:00","status":404,"error":"Not Found","path":"/"}