deno gcp-europe-west2
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: 5733ddf49ff49cd1b885ff43928e6409928e6409928e6409928e6409928e6409
Public Swagger UI/API detected at path: /swagger.json - sample paths:
GET /target/{shortCode}
Open service 34.120.54.55:443 ยท api.np.scantact.me
2026-01-23 14:40
HTTP/1.1 200 OK
content-type: application/javascript
vary: Accept-Encoding
connection: close
content-length: 101
date: Fri, 23 Jan 2026 14:40:20 GMT
via: http/1.1 edgeproxy-h
server: deno/gcp-europe-west2
{"ok":true,"organization":"Scantact, LLC","greeting":"Welcome to the Scantact API","version":"0.6.0"}