Kestrel
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
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 20.206.176.5:443 ยท ac.fecap.br
2026-01-23 12:52
HTTP/1.1 200 OK Content-Length: 1471 Connection: close Content-Type: text/html Date: Fri, 23 Jan 2026 12:52:52 GMT Server: Kestrel Accept-Ranges: bytes Cache-Control: no-cache, no-store, must-revalidate ETag: "1d924910b2569bf" Expires: -1 Last-Modified: Tue, 10 Jan 2023 01:15:36 GMT Page title: Amplia <!doctype html> <html lang="en"> <head> <meta charset="utf-8"> <title>Amplia</title> <base href="/"> <meta name="viewport" content="width=device-width, initial-scale=1"> <link rel="icon" type="image/x-icon" href="theme-assets/favicon"> <!--Custom code begins--> <link href="/api/configuration/css" rel="stylesheet"> <link href="https://fonts.googleapis.com/css?family=Roboto:300,400,500,600" rel="stylesheet"> <!-- https://stackoverflow.com/questions/50371593/angular-6-uncaught-referenceerror-buffer-is-not-defined --> <script> var global = global || window; </script> <!--Custom code ends--> <link rel="stylesheet" href="styles.753c7f7cd1f51fe5fff0.css"></head> <body id="main-theme"> <app-root> <div class="loader-wrapper"> <div class="spinner-eff spinner-eff-4"> <div class="bar bar-top"></div> <div class="bar bar-right"></div> <div class="bar bar-bottom"></div> <div class="bar bar-left"></div> </div> </div> </app-root> <script src="runtime-es2015.b699c06cfb084e98f5de.js" type="module"></script><script src="runtime-es5.b699c06cfb084e98f5de.js" nomodule defer></script><script src="polyfills-es5.f0add322ed28ecb73430.js" nomodule defer></script><script src="polyfills-es2015.ddc2630557b63cd3d84c.js" type="module"></script><script src="main-es2015.1d442ca8c16459f87cc0.js" type="module"></script><script src="main-es5.1d442ca8c16459f87cc0.js" nomodule defer></script></body> </html>