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: 5733ddf49ff49cd1aad03549d0996eeeab0699dbb47d92e9b47d92e9b47d92e9
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: POST /GoogleOAth/GetsGoogleOAth POST /WeisenbrookBot/ServerDiscordEmailBinding POST /api/Auth/login
Open service 172.67.151.213:443 ยท sql-api.weisenbrook.com
2026-01-23 09:07
HTTP/1.1 526 <none> Date: Fri, 23 Jan 2026 09:07:52 GMT Content-Type: text/plain; charset=UTF-8 Content-Length: 15 Connection: close Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 01 Jan 1970 00:00:01 GMT referrer-policy: same-origin Server-Timing: cfEdge;dur=318,cfOrigin;dur=0 x-frame-options: SAMEORIGIN expect-ct: max-age=86400, enforce x-content-type-options: nosniff x-xss-protection: 1; mode=block Server: cloudflare CF-RAY: 9c2624ab6afeaf90-LHR alt-svc: h3=":443"; ma=86400 error code: 526