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: 5733ddf49ff49cd1aad03549a2661a30d2486de95ff45a1740e4fb9296b60477
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/cms/History/{id}
GET /api/Client/gifts
GET /api/Client/history
GET /api/Client/{code}
GET /api/cms/Gift
GET /api/cms/Gift/{id}
GET /api/cms/History
GET /api/cms/Me
POST /api/Client/check
POST /api/Client/open
POST /api/Client/save
POST /api/cms/Auth/login
POST /api/cms/Auth/refresh-token
POST /api/cms/Uploads
PUT /api/cms/Me/change-password/{id}
Open service 104.21.60.212:443 ยท api.gk88mt.com
2026-01-23 00:19
HTTP/1.1 523 <none> Date: Fri, 23 Jan 2026 00:19:41 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 X-Frame-Options: SAMEORIGIN Server: cloudflare CF-RAY: 9c231ea85e7c1e2f-FRA alt-svc: h3=":443"; ma=86400 error code: 523