openresty 1.15.8.1
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: 5733ddf49ff49cd1aad035493301fa85e5635cc6644177a69fadf324948a7b3a
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/Fields/DeleteField/{id}
GET /api/FieldStatus/GetFieldSpaceStatus/{apiKey}
POST /api/Fields/GetField
POST /api/Fields/GetField/{id}
POST /api/Fields/PostField
POST /api/LPRFree/Add
POST /api/LPRFree/Del
POST /api/LPRFree/Get
POST /api/LPRFree/Modify
POST /api/Selector/CarImage
POST /api/Selector/FieldList
POST /api/Selector/SearchCar
POST /api/Selector/SearchCarByField
POST /api/Selector/SearchField
POST /api/Selector/SelectCar
POST /api/Transaction/Close
POST /api/Transaction/Discount/CoBrander
POST /api/Transaction/Discount/CreditCard
POST /api/Transaction/Discount/QRCode
POST /api/Transaction/Discount/Store
POST /api/Transaction/Misc
POST /api/Transaction/Payment/CreditCard
POST /api/Transaction/SessionIdCheckAlive
PUT /api/Fields/PutField/{id}
Open service 157.230.253.7:443 ยท linebot.telexper.com
2026-01-23 11:49
HTTP/1.1 404 Not Found Server: openresty/1.15.8.1 Date: Fri, 23 Jan 2026 11:49:11 GMT Content-Length: 0 Connection: close Strict-Transport-Security: max-age=15724800; includeSubDomains