Byte-nginx
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: 5733ddf49ff49cd1b6e67656b6e67656b6e67656b6e67656b6e67656b6e67656
Public Swagger UI/API detected at path: /swagger-ui.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: 5733ddf49ff49cd1b6e67656b6e67656b6e67656b6e67656b6e67656b6e67656
Public Swagger UI/API detected at path: /swagger-ui.html
Open service 107.155.1.218:80 · trf6gq.com
2026-02-09 09:09
HTTP/1.1 504 Gateway Timeout Server: Byte-nginx Content-Length: 0 Connection: close Date: Mon, 09 Feb 2026 09:09:46 GMT Via: cache02.oversea-US-LAX2,cache01.oversea-US-LAX4 X-Bdcdn-Cache-Status: TCP_MISS,TCP_MISS X-Exception-Info: L3|504 X-Request-Id: 85d1216b2e4eb9de7e7f4698dce4bc02 X-Request-Ip: 164.90.208.56 X-Response-Cache: miss X-Response-Cinfo: 164.90.208.56 X-Tt-Trace-Tag: id=5
Open service 89.222.119.81:443 · trf6gq.com
2026-01-22 21:58
HTTP/1.1 504 Gateway Timeout Server: Byte-nginx Content-Length: 0 Connection: close Date: Thu, 22 Jan 2026 21:58:54 GMT Via: cache02.oversea-NL-AMS2,cache06.oversea-GM-FRA12 X-Bdcdn-Cache-Status: TCP_MISS,TCP_MISS X-Exception-Info: L3|504 X-Request-Id: 336f7ffc2b97f779e35f38032522a349 X-Request-Ip: 146.190.242.161 X-Response-Cache: miss X-Response-Cinfo: 146.190.242.161 X-Tt-Trace-Tag: id=5
Open service 163.53.19.13:443 · trf6gq.com
2026-01-22 21:58
HTTP/1.1 504 Gateway Timeout Server: Byte-nginx Content-Length: 0 Connection: close Date: Thu, 22 Jan 2026 21:58:53 GMT X-Bdcdn-Cache-Status: TCP_HIT X-Exception-Info: L3|504 X-Request-Id: 6c48d946f32262e074cbfc94b7311e26 X-Request-Ip: 209.97.180.8 X-Response-Cache: edge_hit X-Response-Cinfo: 209.97.180.8 X-Tt-Trace-Tag: id=5 via: cache02.oversea-GM-FRA6