AriaNg is visible, but Aria2 RPC on port 6800 is rare in the public count
Aria2 is a command-line download utility with a JSON-RPC interface, and AriaNg is a common browser frontend for it. A count-only ZoomEye measurement produced a large frontend surface: 24,581 title="AriaNg" matches and 37,614 http.body="AriaNg" matches. The direct port="6800" observation returned only 2 matches. Those numbers describe different parts of the deployment chain.
An AriaNg page can be hosted separately from the Aria2 RPC service, proxied through a reverse proxy, or configured to connect to a private address. A public frontend does not prove that the RPC port is publicly reachable. Conversely, a low port count does not prove that the service is safely configured. RPC can be exposed through another port or path, and a frontend loaded from a public page can be used by a browser to reach a reachable backend.
The official aria2 documentation is direct about the control. It recommends a secret authorization token with --rpc-secret, warns that --rpc-listen-all should remain off unless another trusted device needs access, and describes loopback-only listening as the safer default. A JSON-RPC request that changes downloads, writes files, or reads configuration can have real impact even when the service looks like a small download utility.
Review Aria2 deployments from the process and configuration side. Confirm the bind address, RPC port, secret, TLS setting, reverse-proxy path, and browser origin policy. Check whether the RPC secret is embedded in a public AriaNg configuration, a JavaScript file, or a shared dashboard. A secret that is visible to every visitor is not an access control.
For owned services that need remote access, put the RPC interface behind a trusted network and an authenticated proxy, use a unique secret, and restrict browser origins. Keep file-system destinations within the intended download directory and verify that the service account cannot write outside it. Review the API's file-selection and command behavior against the way the deployment is used.
The public AriaNg and body counts are discovery leads for frontend deployments. The port count is a separate measurement with a narrower scope. Do not add the numbers or treat them as the same population. If a page contains an AriaNg title, the owner should check whether it reaches a backend and where that backend is hosted. If a host exposes port 6800, verify the RPC configuration before testing any method that changes state.
The small port count also illustrates why a public search cannot replace internal inventory. Many RPC services are bound to loopback or a VPN and will not appear in a global port query. An SSH tunnel, a container network, or a reverse proxy can expose the same authority through a different address. The defensible question is where the RPC secret and file-write authority live, not whether port 6800 is globally visible.