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.66.0.125:443 ยท pl-cdn.mcbtest.dk
2026-01-23 09:29
HTTP/1.1 404 Not Found
Date: Fri, 23 Jan 2026 09:29:30 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Server: cloudflare
CF-Ray: 9c26445f389c63eb-LHR
CF-Cache-Status: DYNAMIC
x-powered-by: ASP.NET
Set-Cookie: __cf_bm=FToxbLgqymTe6_IHfkABIYgFy1AbqamSmpQXLX1s2YI-1769160570-1.0.1.1-CvIHuJO_N7DC8qpG8uvZ4_914Q0fGwL1fb_Mq5EI0i_201ybqmjYs9XBGQefs5XZAYRfYDSJtFQKnL0Vbm_CODzpHX6Ew.sp2367A.cBzqk; path=/; expires=Fri, 23-Jan-26 09:59:30 GMT; domain=.pl-cdn.mcbtest.dk; HttpOnly; Secure; SameSite=None
alt-svc: h3=":443"; ma=86400
Page title: Page Not Found
<!doctype html>
<html class="no-js" lang="en">
<head>
<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.0, maximum-scale=1.0, user-scalable=no">
<title>Page Not Found</title>
<link rel="stylesheet" href="/umbraco/assets/css/nonodes.style.min.css" />
<style type="text/css">
body {
color:initial;
}
section {
background: none;
}
section a, section a:focus, section a:visited {
color:initial;
border-color:currentColor;
}
</style>
</head>
<body>
<section>
<article>
<div>
<h1>Page Not Found</h1>
<h3>No template exists to render the document at URL '/'.</h3>
<div class="cta"></div>
<div class="row">
<div class="col">
<h2>This page can be replaced</h2>
<p>
Custom error handling might make your site look more on-brand and minimize the impact of errors on user experience - for example, a custom 404 with some helpful links (or a search function) could bring some value to the site.
</p>
<a href="https://umbra.co/custom-error-pages" target="_blank" rel="noopener">Implementing custom error pages →</a>
</div>
<div class="col">
<h2>Be a part of the community</h2>
<p>The Umbraco community is the best of its kind, be sure to visit, and if you have any questions, we're sure that you can get your answers from the community.</p>
<a href="https://our.umbraco.com/" target="_blank" rel="noopener">our.Umbraco →</a>
</div>
</div>
</div>
</article>
</section>
</body>
</html>