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: 5733ddf49ff49cd1926e27d0926e27d0926e27d0926e27d0926e27d0926e27d0
Public Swagger UI/API detected at path: /webjars/swagger-ui/index.html
Open service 104.21.227.134:443 ยท pdf.shusite.top
2026-01-23 08:19
HTTP/1.1 200 OK
Date: Fri, 23 Jan 2026 08:19:26 GMT
Content-Type: text/html;charset=utf-8
Transfer-Encoding: chunked
Connection: close
Server: cloudflare
vary: Accept-Encoding
content-language: en-US
strict-transport-security: max-age=31536000
alt-svc: h3=":443"; ma=86400
Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=vGdI%2F2aYOnfRlxgQS48MbJlNMsS7JFJhUwkI7GxZqtK3Io3vFcJ3UGUm6qFUMRZV1UhALGaI3Ak7wDclN7QTFFqCut9ebB%2FgROMz0ZGJkw%3D%3D"}]}
cf-cache-status: DYNAMIC
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
CF-RAY: 9c25ddb4b8c56687-AMS