Tengine
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: 5733ddf49ff49cd1bf890109bf890109bf890109bf890109bf890109bf890109
Public Swagger UI/API detected at path: /api-docs/swagger.json
Open service 61.170.77.81:443 ยท aojiarui.com
2026-01-23 10:03
HTTP/1.1 200 OK Server: Tengine Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Connection: close Vary: Accept-Encoding Date: Fri, 23 Jan 2026 10:03:30 GMT Vary: Accept-Encoding X-Powered-By: Express Cache-Control: public, max-age=60 Cloudflare-CDN-Cache-Control: max-age=600, stale-while-revalidate=30 ETag: W/"af18-P9RNUgbJ08U4FJ6sMHbUKNHfWyU" Via: cache6.l2cm9-7[31,0], ens-cache6.cn6020[78,0] Timing-Allow-Origin: * EagleId: 3daa4d1a17691626104368665e