openresty
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: 5733ddf49ff49cd1926e27d0926e27d0926e27d0926e27d0926e27d0926e27d0
Public Swagger UI/API detected at path: /webjars/swagger-ui/index.html
Open service 43.159.98.20:443 ยท tenyon.cn
2026-01-23 02:26
HTTP/1.1 200 OK
server: openresty
content-type: text/html
vary: Accept-Encoding
vary: Origin
vary: Access-Control-Request-Method
vary: Access-Control-Request-Headers
content-language: zh-CN
pragma: no-cache
expires: 0
x-content-type-options: nosniff
strict-transport-security: max-age=31536000
x-frame-options: SAMEORIGIN
x-xss-protection: 0
referrer-policy: strict-origin-when-cross-origin
set-cookie: XSRF-TOKEN=21487b7e-5c42-4b9f-b090-e80cb8709ec2; Path=/; HTTPOnly
alt-svc: h3=":443"; ma=2592000
Cache-Control: must-revalidate, no-cache, no-store, max-age=0
Transfer-Encoding: chunked
Connection: close
X-Frame-Options: SAMEORIGIN
Date: Fri, 23 Jan 2026 02:26:53 GMT
EO-LOG-UUID: 5264522680387630670
EO-Cache-Status: MISS
NEL: {"success_fraction":0.1,"report_to":"eo-nel","max_age":604800}
Report-To: {"endpoints":[{"url":"https://nel.teo-rum.com/eo-cgi/nel"}],"group":"eo-nel","max_age":604800}