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: 5733ddf49ff49cd1f3d88d60b939a20553200b10710ae6ad101dccf2be62e41f
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths:
DELETE /Routyn/trip/{externalTripId}
DELETE /Routyn/vanloadstop/{externalVanLoadStopId}
GET /IWebCustomer/GetCustomerByCnp
GET /IWebCustomer/GetCustomerByDeviceSerialNumber
POST /CTI/Output/StartCall
POST /CardReadings/UpdateFileStatus
POST /EmailManagement/PublishEmail
POST /PatientProtocolAiEngine/CreateIntervention
POST /Routyn/trip
POST /Routyn/vanloadstop
POST /Sms/delivered-messages/{countryId}
POST /Sms/failed-messages/{countryId}
POST /Sms/messages/{countryId}
PUT /Routyn/address
PUT /Routyn/service
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549cd8eb320a589261db4afa4b494e2a06d2946ee52
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /Routyn/trip/{externalTripId}
DELETE /Routyn/vanloadstop/{externalVanLoadStopId}
GET /IWebCustomer/GetCustomerByCnp
GET /IWebCustomer/GetCustomerByDeviceSerialNumber
POST /CTI/Output/StartCall
POST /CardReadings/UpdateFileStatus
POST /EmailManagement/PublishEmail
POST /PatientProtocolAiEngine/CreateIntervention
POST /Routyn/trip
POST /Routyn/vanloadstop
POST /Sms/delivered-messages/{countryId}
POST /Sms/failed-messages/{countryId}
POST /Sms/messages/{countryId}
PUT /Routyn/address
PUT /Routyn/service
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: 5733ddf49ff49cd1aad03549cd8eb320a589261db4afa4b494e2a06d2946ee52
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /Routyn/trip/{externalTripId}
DELETE /Routyn/vanloadstop/{externalVanLoadStopId}
GET /IWebCustomer/GetCustomerByCnp
GET /IWebCustomer/GetCustomerByDeviceSerialNumber
POST /CTI/Output/StartCall
POST /CardReadings/UpdateFileStatus
POST /EmailManagement/PublishEmail
POST /PatientProtocolAiEngine/CreateIntervention
POST /Routyn/trip
POST /Routyn/vanloadstop
POST /Sms/delivered-messages/{countryId}
POST /Sms/failed-messages/{countryId}
POST /Sms/messages/{countryId}
PUT /Routyn/address
PUT /Routyn/service
Open service 2.16.183.16:443 · tst.api.trcservices.hc.linde.com
2026-01-23 13:16
HTTP/1.1 404 Not Found Content-Length: 0 Server: Microsoft-IIS/10.0 Request-Context: appId=cid-v1:00242a04-7ea3-439e-83c2-90c69c144e5f X-Powered-By: ASP.NET Date: Fri, 23 Jan 2026 13:16:41 GMT Connection: close Set-Cookie: ARRAffinity=bba6a6c94b78ab034721ea71373c3ccc43526320ca2c7c2e293cd8a272047f85;Path=/;HttpOnly;Secure;Domain=tst.api.trcservices.hc.linde.com Set-Cookie: ARRAffinitySameSite=bba6a6c94b78ab034721ea71373c3ccc43526320ca2c7c2e293cd8a272047f85;Path=/;HttpOnly;SameSite=None;Secure;Domain=tst.api.trcservices.hc.linde.com
Open service 2.16.183.16:443 · api.trcservices.hc.linde.com
2026-01-23 13:16
HTTP/1.1 404 Not Found Content-Length: 0 Server: Microsoft-IIS/10.0 Request-Context: appId=cid-v1:275b01f6-3d9e-40ae-91ce-3e15612d1429 X-Powered-By: ASP.NET Date: Fri, 23 Jan 2026 13:16:41 GMT Connection: close
Open service 2.16.183.16:80 · tst.api.trcservices.hc.linde.com
2026-01-23 13:16
HTTP/1.1 301 Moved Permanently Content-Length: 0 Location: https://tst.api.trcservices.hc.linde.com/ Date: Fri, 23 Jan 2026 13:17:03 GMT Connection: close
Open service 2.16.183.12:80 · tst.api.trcservices.hc.linde.com
2026-01-23 13:16
HTTP/1.1 301 Moved Permanently Content-Length: 0 Location: https://tst.api.trcservices.hc.linde.com/ Date: Fri, 23 Jan 2026 13:17:04 GMT Connection: close
Open service 2.16.183.12:443 · tst.api.trcservices.hc.linde.com
2026-01-23 13:16
HTTP/1.1 404 Not Found Content-Length: 0 Server: Microsoft-IIS/10.0 Request-Context: appId=cid-v1:00242a04-7ea3-439e-83c2-90c69c144e5f X-Powered-By: ASP.NET Date: Fri, 23 Jan 2026 13:16:41 GMT Connection: close Set-Cookie: ARRAffinity=bba6a6c94b78ab034721ea71373c3ccc43526320ca2c7c2e293cd8a272047f85;Path=/;HttpOnly;Secure;Domain=tst.api.trcservices.hc.linde.com Set-Cookie: ARRAffinitySameSite=bba6a6c94b78ab034721ea71373c3ccc43526320ca2c7c2e293cd8a272047f85;Path=/;HttpOnly;SameSite=None;Secure;Domain=tst.api.trcservices.hc.linde.com
Open service 2.16.183.12:443 · api.trcservices.hc.linde.com
2026-01-23 13:16
HTTP/1.1 404 Not Found Content-Length: 0 Server: Microsoft-IIS/10.0 Request-Context: appId=cid-v1:275b01f6-3d9e-40ae-91ce-3e15612d1429 X-Powered-By: ASP.NET Date: Fri, 23 Jan 2026 13:16:41 GMT Connection: close
Open service 2.16.183.16:80 · api.trcservices.hc.linde.com
2026-01-23 13:16
HTTP/1.1 301 Moved Permanently Content-Length: 0 Location: https://api.trcservices.hc.linde.com/ Date: Fri, 23 Jan 2026 13:17:04 GMT Connection: close
Open service 2.16.183.12:80 · api.trcservices.hc.linde.com
2026-01-23 13:16
HTTP/1.1 301 Moved Permanently Content-Length: 0 Location: https://api.trcservices.hc.linde.com/ Date: Fri, 23 Jan 2026 13:17:03 GMT Connection: close