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: 5733ddf49ff49cd1aad035493a5f55143a5f55143a5f55143a5f55143a5f5514
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: POST /analyze
Open service 13.67.63.90:80 · ai-staging.traxia.cloud
2026-01-12 09:44
HTTP/1.1 301 Moved Permanently Content-Length: 0 Connection: close Date: Mon, 12 Jan 2026 09:45:40 GMT Location: https://ai-staging.traxia.cloud/
Open service 13.67.63.90:443 · ai-staging.traxia.cloud
2026-01-12 09:44
HTTP/1.1 404 Not Found Content-Length: 0 Connection: close Date: Mon, 12 Jan 2026 09:45:41 GMT Server: Microsoft-IIS/10.0 Set-Cookie: ARRAffinity=db8b43a1f74b7929a21f90db2f7543bf89a63261ba47d2dc4da530aec375a3a1;Path=/;HttpOnly;Secure;Domain=ai-staging.traxia.cloud Set-Cookie: ARRAffinitySameSite=db8b43a1f74b7929a21f90db2f7543bf89a63261ba47d2dc4da530aec375a3a1;Path=/;HttpOnly;SameSite=None;Secure;Domain=ai-staging.traxia.cloud X-Powered-By: ASP.NET