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: 5733ddf49ff49cd1f3d88d60698956ff98d46ded7e21297f92698464ce1518a8
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths:
GET /api/v1/resources/{calendarResourceId}
GET /api/v1/resources/{resourceId}/event/{eventId}
POST /api/v1/microsoft365/events/notify
POST /api/v1/resources
POST /api/v1/resources/list
POST /api/v1/resources/{calendarResourceId}/availability
POST /api/v1/resources/{calendarResourceId}/events
POST /api/v1/resources/{resourceId}/event
POST /api/v1/resources/{resourceId}/event/{eventId}/cancel
POST /api/v1/resources/{resourceId}/event/{eventId}/recurring-events
PUT /api/v1/resources/{resourceId}/subcription
Open service 20.50.2.7:443 ยท calendar.api.vib.be
2026-01-23 13:14
HTTP/1.1 301 Moved Permanently Content-Length: 0 Connection: close Date: Fri, 23 Jan 2026 13:15:15 GMT Server: Kestrel Location: index.html