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: 5733ddf49ff49cd1aad035497f01cd57a7f19077992775fbd46add6d14f22f47
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/user-settings/{id}
GET /api/v1/clients
GET /api/v1/clients/{clientId}/configuration
GET /api/v1/clients/{clientId}/organizations
GET /api/v1/clients/{clientId}/packages
GET /api/v1/clients/{clientId}/users
GET /api/v1/communications/{id}
GET /api/v1/invoices
GET /api/v1/invoices/organizations
GET /api/v1/invoices/{invoiceId}
GET /api/v1/invoices/{invoiceId}/candidate-summary
GET /api/v1/invoices/{invoiceId}/documents/{documentId}
GET /api/v1/invoices/{invoiceId}/get-document
GET /api/v1/invoices/{invoiceId}/organization-reference-code-summary
GET /api/v1/invoices/{invoiceId}/organization-summary
GET /api/v1/invoices/{invoiceId}/organization-summary-details
GET /api/v1/invoices/{invoiceId}/organizations
GET /api/v1/invoices/{invoiceId}/reference-code-summary
GET /api/v1/notifications
GET /api/v1/order-statuses
GET /api/v1/orders
GET /api/v1/orders/{orderId}/actions
GET /api/v1/orders/{orderId}/activities
GET /api/v1/orders/{orderId}/candidate
GET /api/v1/orders/{orderId}/disputable-searches
GET /api/v1/orders/{orderId}/documents
GET /api/v1/orders/{orderId}/documents/{documentId}
GET /api/v1/orders/{orderId}/documents/{documentId}/content
GET /api/v1/orders/{orderId}/progress
GET /api/v1/product-relations
GET /api/v1/products
GET /api/v1/reports/all-orders/statistics
GET /api/v1/reports/all-orders/status-counts
GET /api/v1/reports/all-orders/table
GET /api/v1/search/omni
GET /api/v1/session
GET /api/v1/states
GET /api/v1/user-settings
GET /api/v1/widgets
GET /api/v1/widgets/1
GET /api/v1/widgets/10
GET /api/v1/widgets/11
GET /api/v1/widgets/2
GET /api/v1/widgets/3
GET /api/v1/widgets/4
GET /api/v1/widgets/5
GET /api/v1/widgets/6
GET /api/v1/widgets/7
GET /api/v1/widgets/8
GET /api/v1/widgets/9
POST /api/v1/communications/{id}/replies
POST /api/v1/notifications/{notificationId}/mark-as-read
POST /api/v1/order-archives
POST /api/v1/order-batch-downloads
POST /api/v1/orders/cancel
POST /api/v1/orders/{orderId}/disputes
POST /api/v1/reports/all-orders/table-exports
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: 5733ddf49ff49cd1aad035497f01cd57a7f19077992775fbd46add6d14f22f47
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/v1/user-settings/{id}
GET /api/v1/clients
GET /api/v1/clients/{clientId}/configuration
GET /api/v1/clients/{clientId}/organizations
GET /api/v1/clients/{clientId}/packages
GET /api/v1/clients/{clientId}/users
GET /api/v1/communications/{id}
GET /api/v1/invoices
GET /api/v1/invoices/organizations
GET /api/v1/invoices/{invoiceId}
GET /api/v1/invoices/{invoiceId}/candidate-summary
GET /api/v1/invoices/{invoiceId}/documents/{documentId}
GET /api/v1/invoices/{invoiceId}/get-document
GET /api/v1/invoices/{invoiceId}/organization-reference-code-summary
GET /api/v1/invoices/{invoiceId}/organization-summary
GET /api/v1/invoices/{invoiceId}/organization-summary-details
GET /api/v1/invoices/{invoiceId}/organizations
GET /api/v1/invoices/{invoiceId}/reference-code-summary
GET /api/v1/notifications
GET /api/v1/order-statuses
GET /api/v1/orders
GET /api/v1/orders/{orderId}/actions
GET /api/v1/orders/{orderId}/activities
GET /api/v1/orders/{orderId}/candidate
GET /api/v1/orders/{orderId}/disputable-searches
GET /api/v1/orders/{orderId}/documents
GET /api/v1/orders/{orderId}/documents/{documentId}
GET /api/v1/orders/{orderId}/documents/{documentId}/content
GET /api/v1/orders/{orderId}/progress
GET /api/v1/product-relations
GET /api/v1/products
GET /api/v1/reports/all-orders/statistics
GET /api/v1/reports/all-orders/status-counts
GET /api/v1/reports/all-orders/table
GET /api/v1/search/omni
GET /api/v1/session
GET /api/v1/states
GET /api/v1/user-settings
GET /api/v1/widgets
GET /api/v1/widgets/1
GET /api/v1/widgets/10
GET /api/v1/widgets/11
GET /api/v1/widgets/2
GET /api/v1/widgets/3
GET /api/v1/widgets/4
GET /api/v1/widgets/5
GET /api/v1/widgets/6
GET /api/v1/widgets/7
GET /api/v1/widgets/8
GET /api/v1/widgets/9
POST /api/v1/communications/{id}/replies
POST /api/v1/notifications/{notificationId}/mark-as-read
POST /api/v1/order-archives
POST /api/v1/order-batch-downloads
POST /api/v1/orders/cancel
POST /api/v1/orders/{orderId}/disputes
POST /api/v1/reports/all-orders/table-exports
Open service 20.119.0.39:443 · stg-ucp-be.clairiti.com
2026-01-22 22:29
HTTP/1.1 404 Not Found Content-Length: 0 Connection: close Date: Thu, 22 Jan 2026 22:29:29 GMT Server: Kestrel Request-Context: appId=cid-v1:8efead58-34e7-4a4f-bea6-c2b64d418d7b
Open service 20.119.0.39:443 · stg-ucp-be.clairiti.com
2026-01-10 02:26
HTTP/1.1 404 Not Found Content-Length: 0 Connection: close Date: Sat, 10 Jan 2026 02:27:34 GMT Server: Kestrel Request-Context: appId=cid-v1:8efead58-34e7-4a4f-bea6-c2b64d418d7b