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: 5733ddf49ff49cd1aad03549092f8edb5d9e7cbfe289c682b83e1544761b0e4a
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/Tas/Command
GET /api/v1/Tas/Devices
GET /api/v1/Tas/Devices/{serial}
GET /api/v1/Tas/TestDevices
GET /api/v1/Tas/TestDevices/{serial}
GET /api/v1/Tas/tunnel
GET /api/v1/Tas/version
POST /api/v1/Tas/Command/{serial}
Open service 104.18.37.28:443 ยท rashub.dev.sesami.io
2026-01-23 04:12
HTTP/1.1 404 Not Found Date: Fri, 23 Jan 2026 04:12:14 GMT Content-Length: 0 Connection: close strict-transport-security: max-age=15724800; includeSubDomains cf-cache-status: DYNAMIC Server: cloudflare CF-RAY: 9c24739f1acbf551-FRA