Byte-nginx
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
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 89.222.119.81:443 ยท hopenapi.llzhy.com
2026-01-22 22:53
HTTP/1.1 404 Not Found Server: Byte-nginx Content-Length: 0 Connection: close Date: Thu, 22 Jan 2026 22:53:06 GMT Vary: Access-Control-Request-Headers, Access-Control-Request-Method, Origin Via: cache11.CN-HK-HKG8,cache03.oversea-GM-FRA3,cache06.oversea-GM-FRA12 X-Bdcdn-Cache-Status: TCP_MISS,TCP_MISS,TCP_MISS X-Exception-Info: O3|404 X-Request-Id: c04b3e6250db246b07fcef4585e13431 X-Request-Ip: 206.81.12.187 X-Response-Cache: miss X-Response-Cinfo: 206.81.12.187 X-Tt-Trace-Tag: id=5