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: 5733ddf49ff49cd1926e27d0926e27d0926e27d0926e27d0926e27d0926e27d0
Public Swagger UI/API detected at path: /webjars/swagger-ui/index.html
Open service 104.21.227.134:443 ยท blog.berryexpress.top
2026-01-23 09:58
HTTP/1.1 301 Moved Permanently
Date: Fri, 23 Jan 2026 09:58:13 GMT
Content-Length: 0
Connection: close
Location: https://berryhub.org/
Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=4BlFMhW2%2Fk9ZLEA105zVs96lninsxZBcs36gMbUkSIKqkXvGytdCE3Y9lC1MU%2Bf2nYdUUy1ZrGGq%2BB4oy7nZ%2BjnphgxgK01wRSiWmRhiwKu3m7Yurg%3D%3D"}]}
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Server: cloudflare
CF-RAY: 9c266e70ee519733-FRA