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.67.204.83:443 ยท atom-api.maysoft.io
2026-01-23 07:04
HTTP/1.1 404 Not Found
Date: Fri, 23 Jan 2026 07:04:41 GMT
Content-Length: 0
Connection: close
strict-transport-security: max-age=31536000; includeSubDomains
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-cache-status: DYNAMIC
Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=m7n4EfOFDsnd806CeLJQe1qPFchAv4sK6HFNsI4ruJtPC9u%2BgS%2F0nq0AHaZyo7Z8KvNBIzNfjPqOPDA9dgOBBDPHavqrifTDSu91jTFwPr%2BF7bA%3D"}]}
Server: cloudflare
CF-RAY: 9c2570370b376acc-FRA
alt-svc: h3=":443"; ma=86400