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: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Open service 74.125.29.121:443 · utils-api.aiai.now
2026-01-09 05:28
HTTP/1.1 404 Not Found
content-type: application/json
x-cloud-trace-context: b1a223a3b3d13aa4e73629af33087f65
date: Fri, 09 Jan 2026 05:28:19 GMT
server: Google Frontend
Content-Length: 22
Connection: close
{"detail":"Not Found"}
Open service 74.125.29.121:443 · utils-api.aiai.now
2026-01-02 07:42
Open service 74.125.29.121:443 · utils-api.aiai.now
2025-12-22 15:24
Open service 74.125.29.121:443 · utils-api.aiai.now
2025-12-20 17:28
HTTP/1.1 404 Not Found
content-type: application/json
x-cloud-trace-context: 7a9006284207f859e2b87f7e858d198f
date: Sat, 20 Dec 2025 17:28:14 GMT
server: Google Frontend
Content-Length: 22
Connection: close
{"detail":"Not Found"}