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: 5733ddf49ff49cd1aad0354977346cbea6e9af88f48c179ee9830a4ddc2c700a
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
POST /v1/Auth/login
POST /v1/OrganizationUnit
POST /v1/notifications/mail-delegation
POST /v1/notifications/user-data-changed
POST /v1/notifications/user-invite-result
POST /v1/notifications/user-merge
POST /v1/notifications/user-status-changed
PUT /v1/OrganizationUnit/{id}
Open service 20.105.224.34:443 ยท api-ext-test.crossvertise.com
2026-01-23 04:31
HTTP/1.1 404 Not Found Content-Length: 0 Connection: close Date: Fri, 23 Jan 2026 04:32:29 GMT Server: Kestrel Request-Context: appId=cid-v1:a2a39f46-0ad7-4fb7-9187-312a394c6b63