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 52.143.247.27:443 · secure-api.americommerce.com
2026-01-09 11:35
HTTP/1.1 404 Not Found Strict-Transport-Security: max-age=31536000 Date: Fri, 09 Jan 2026 11:35:59 GMT Transfer-Encoding: chunked Connection: close
Open service 52.143.247.27:443 · secure-api.americommerce.com
2026-01-02 03:06
HTTP/1.1 404 Not Found Strict-Transport-Security: max-age=31536000 Date: Fri, 02 Jan 2026 03:06:59 GMT Transfer-Encoding: chunked Connection: close
Open service 52.143.247.27:443 · secure-api.americommerce.com
2025-12-22 17:05
HTTP/1.1 404 Not Found Strict-Transport-Security: max-age=31536000 Date: Mon, 22 Dec 2025 17:05:32 GMT Transfer-Encoding: chunked Connection: close