Microsoft-IIS 10.0
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: 5733ddf49ff49cd1aad035491855fed41884c4f5536eb8ec536eb8ec536eb8ec
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/appointment/{tenantId}
GET /api/patient/{tenantId}/{external_id}
POST /api/patient/{tenantId}
Open service 20.118.48.5:443 ยท crmconnector.eivfconnect.com
2026-01-22 11:56
HTTP/1.1 200 OK Connection: close Content-Type: text/plain; charset=utf-8 Date: Thu, 22 Jan 2026 11:57:16 GMT Server: Microsoft-IIS/10.0 Set-Cookie: ARRAffinity=d8694fc96d9a9dc9079c20e876c5c701826cf146c68ab5f43b7c4e6c69aa01e1;Path=/;HttpOnly;Secure;Domain=crmconnector.eivfconnect.com Set-Cookie: ARRAffinitySameSite=d8694fc96d9a9dc9079c20e876c5c701826cf146c68ab5f43b7c4e6c69aa01e1;Path=/;HttpOnly;SameSite=None;Secure;Domain=crmconnector.eivfconnect.com Transfer-Encoding: chunked Request-Context: appId=cid-v1:d9a3dcab-6d88-4fa8-b1be-c264b1e7ffcd X-Powered-By: ASP.NET Always On