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: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Open service 13.69.68.16:443 ยท api.datamodeldesigner.io
2026-01-23 03:52
HTTP/1.1 404 Not Found Content-Length: 0 Connection: close Date: Fri, 23 Jan 2026 03:52:41 GMT Server: Microsoft-IIS/10.0 Set-Cookie: ARRAffinity=c2092019ec54877be346fdd841e01c0cd676e624844bf6d86f817830b265cbf7;Path=/;HttpOnly;Secure;Domain=api.datamodeldesigner.io Set-Cookie: ARRAffinitySameSite=c2092019ec54877be346fdd841e01c0cd676e624844bf6d86f817830b265cbf7;Path=/;HttpOnly;SameSite=None;Secure;Domain=api.datamodeldesigner.io Request-Context: appId=cid-v1:e60577b6-36ae-4cbe-9d0b-25930fcc8264 X-Powered-By: ASP.NET