TencentEdgeOne
tcp/443 tcp/80
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 43.159.98.35:443 · txqetu2.ijlty.com
2026-01-22 20:34
HTTP/1.1 418 Unknown Status Content-Length: 0 Connection: close Server: TencentEdgeOne EO-LOG-UUID: 4277306131162610472 Date: Thu, 22 Jan 2026 20:35:05 GMT
Open service 43.159.98.35:80 · txqetu2.ijlty.com
2026-01-22 20:03
HTTP/1.1 418 Unknown Status Content-Length: 0 Connection: close Server: TencentEdgeOne EO-LOG-UUID: 1216762619107185103 Date: Thu, 22 Jan 2026 20:03:29 GMT