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: 5733ddf49ff49cd1aad0354967330e2673c3dd4390462528e6b08e23e6b08e23
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /AgentListner/api/getData GET /AgentListner/api/getLastUpdateTime GET /AgentListner/api/getVersion POST /AgentListner/api/postData
Open service 104.26.2.3:443 ยท agent.nsyteful.com
2026-01-23 11:44
HTTP/1.1 404 Not Found
Date: Fri, 23 Jan 2026 11:44:17 GMT
Content-Length: 0
Connection: close
Server: cloudflare
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=eAKmH%2F6ETRgvqNYPeWL1Owqr8SDzF2ZSt4B38VtyDhZJ3%2Ba0wnAhCZ89G6hrYVf9HMW7Ypxk00fkKg7OFRyIe12crRRZu4odT6wxVB1RhUKp"}]}
CF-RAY: 9c2709ca9d5e4299-EWR