cloudflare
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 172.67.213.253:443 ยท requests.bullypanel.com
2026-01-23 12:01
HTTP/1.1 307 Temporary Redirect
Date: Fri, 23 Jan 2026 12:01:12 GMT
Transfer-Encoding: chunked
Connection: close
Server: cloudflare
x-powered-by: Express
location: /login
cf-cache-status: DYNAMIC
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=vyivz8v%2FHtLuZaA1HyW9%2FMCR8miUl6dloCBQ4AB7Bk3l49voxxf6TpcxINwFHpMIPZsaD0ck6bhvYJjy3QkPTMRlF1MgEMtFmWfRvrYsncv%2Fam8S1A%3D%3D"}]}
CF-RAY: 9c2722935fcaf664-LHR
alt-svc: h3=":443"; ma=86400