Kestrel
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: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Open service 51.104.28.88:443 · sample.suregifts.com
2026-01-22 20:24
HTTP/1.1 200 OK Connection: close Date: Thu, 22 Jan 2026 20:24:55 GMT Server: Kestrel Transfer-Encoding: chunked -OK
Open service 51.104.28.88:443 · sample.suregifts.com
2026-01-08 21:47
HTTP/1.1 200 OK Connection: close Date: Thu, 08 Jan 2026 21:48:03 GMT Server: Kestrel Transfer-Encoding: chunked -OK
Open service 51.104.28.88:443 · sample.suregifts.com
2026-01-01 22:04
HTTP/1.1 200 OK Connection: close Date: Thu, 01 Jan 2026 22:04:23 GMT Server: Kestrel Transfer-Encoding: chunked -OK