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: 5733ddf49ff49cd1f3d88d609d6f329520763ca69ca326f4c0e10745c0e10745
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths: GET /View/Coupon GET /checkHealth GET /ecoupons/api/checkcode POST /ecoupons/api/usecode
Open service 23.36.162.221:80 ยท taskercoupon.lppsa.com
2026-02-02 17:51
HTTP/1.1 301 Moved Permanently Content-Length: 0 Location: https://taskercoupon.lppsa.com/ Expires: Mon, 02 Feb 2026 17:51:25 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Mon, 02 Feb 2026 17:51:25 GMT Connection: close