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: 5733ddf49ff49cd1aad03549330b5f901156dd9e5bfedbface2e37df90c5163a
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/InAppCompanies
GET /api/Registrations
GET /api/Registrations/{employeeId}
GET /api/Registrations/{registrationCode}
POST /api/ImageUpload
POST /api/ProcessManager
POST /api/TimesheetManager
Open service 51.140.210.102:443 ยท www.pipelayer.info
2026-01-23 04:07
HTTP/1.1 302 Found Content-Length: 0 Connection: close Date: Fri, 23 Jan 2026 04:08:24 GMT Server: Microsoft-IIS/10.0 Location: /Identity/Account/Login Set-Cookie: ARRAffinity=82818a591ed6cc61bd9adb9f6d0f6b0d48f4f4bf1e9f71ae1b137001e6a90551;Path=/;HttpOnly;Secure;Domain=www.pipelayer.info Set-Cookie: ARRAffinitySameSite=82818a591ed6cc61bd9adb9f6d0f6b0d48f4f4bf1e9f71ae1b137001e6a90551;Path=/;HttpOnly;SameSite=None;Secure;Domain=www.pipelayer.info Strict-Transport-Security: max-age=2592000 X-Powered-By: ASP.NET