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 40.121.32.232:443 · demo-reportingdataapi.dev.autodatadigitaldealer.com
2026-01-23 13:22
HTTP/1.1 302 Found Content-Length: 0 Connection: close Date: Fri, 23 Jan 2026 13:22:50 GMT Server: Kestrel Cache-Control: no-cache, no-store, max-age=0, must-revalidate Location: /swagger Pragma: no-cache Strict-Transport-Security: max-age=2592000
Open service 40.121.32.232:80 · demo-reportingdataapi.dev.autodatadigitaldealer.com
2026-01-11 23:00
HTTP/1.1 301 Moved Permanently Content-Length: 0 Connection: close Date: Sun, 11 Jan 2026 23:01:35 GMT Location: https://demo-reportingdataapi.dev.autodatadigitaldealer.com/
Open service 40.121.32.232:443 · demo-reportingdataapi.dev.autodatadigitaldealer.com
2026-01-11 23:00
HTTP/1.1 302 Found Content-Length: 0 Connection: close Date: Sun, 11 Jan 2026 23:01:36 GMT Server: Kestrel Cache-Control: no-cache, no-store, max-age=0, must-revalidate Location: /swagger Pragma: no-cache Strict-Transport-Security: max-age=2592000