cloudflare
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 172.64.147.174:443 · slhs01mstr6p0ppinte.dxcloud.episerver.net
2026-01-23 10:38
HTTP/1.1 404 Not Found
Date: Fri, 23 Jan 2026 10:38:50 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
CF-RAY: 9c26a9ee6b41d7a5-LHR
Cache-Control: no-store,no-cache
Pragma: no-cache
Set-Cookie: EPiStateMarker=true; path=/; secure
Set-Cookie: EPiNumberOfVisits=1%2C2026-01-23T10%3A38%3A50; expires=Sat, 23 Jan 2027 10:38:50 GMT; path=/; secure; httponly
Set-Cookie: ARRAffinity=8a49adf40f127c11723a54c4ec375c3d08102b5f5048d437bb3d504272b2b06c;Path=/;HttpOnly;Secure;Domain=slhs01mstr6p0ppinte.dxcloud.episerver.net
Set-Cookie: ARRAffinitySameSite=8a49adf40f127c11723a54c4ec375c3d08102b5f5048d437bb3d504272b2b06c;Path=/;HttpOnly;SameSite=None;Secure;Domain=slhs01mstr6p0ppinte.dxcloud.episerver.net
Strict-Transport-Security: max-age=2592000
Request-Context: appId=cid-v1:6f8efab9-9d3a-4398-8d34-7dbbd0ec94d3
cf-cache-status: DYNAMIC
Server: cloudflare
alt-svc: h3=":443"; ma=86400
Page title: Resource Not Found
<!DOCTYPE html>
<html lang="en">
<head>
<title>Resource Not Found</title>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link type="image/x-icon" rel="shortcut icon" href="/Util/images/favicon.ico" />
<link type="text/css" rel="stylesheet" href="/Util/styles/errorpage.css" />
</head>
<body class="epi-workspace">
<div class="error-wrapper">
<div class="friendly-error">
<h1 class="fiendly-error-header">Resource Not Found</h1>
<p class="fiendly-error-content">Unfortunately, the resource you’re looking for couldn’t be found or does not exist anymore.</p>
</div>
</div>
</body>
</html>