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.18.185.26:443 · scmk.flowcld.com
2026-01-23 14:35
HTTP/1.1 200 OK
Date: Fri, 23 Jan 2026 14:35:38 GMT
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Server: cloudflare
vary: Origin
vary: Access-Control-Request-Method
vary: Access-Control-Request-Headers
trace-id:
x-content-type-options: nosniff
x-xss-protection: 0
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
pragma: no-cache
expires: 0
strict-transport-security: max-age=31536000
cf-cache-status: DYNAMIC
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Speculation-Rules: "/cdn-cgi/speculation"
Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=WBNCni%2BDEF1JkTd5Fcx5h3INvOR%2FoaxCb9fgUKp%2F%2F%2BoThOxMlEQ%2FqqAIIWrg5HkxyhbClwsSNP81ESkxi%2BZJX2UiJqU8jPgqwpchtesSVtY%3D"}]}
CF-RAY: 9c2804c85d7cd278-FRA
alt-svc: h3=":443"; ma=86400
{"code":401,"data":null,"msg":"账号未登录"}