Registered for BOINC client control, but the BOINC client actually listens on 31416 — the registration does not match the shipping software.
IANA assigns 1043 to boinc-client, "BOINC Client Control", registered in 2004 by BOINC's project lead. BOINC is Berkeley's volunteer distributed-computing platform, and its client exposes a GUI RPC interface that managers such as BOINC Manager connect to — but that interface listens on TCP 31416, not 1043, and can be moved with --gui_rpc_port. So the registration is stale relative to the software: seeing 1043 open does not indicate BOINC, while seeing 31416 open does. The GUI RPC port binds to localhost by default and is guarded by a password in gui_rpc_auth.cfg.
Do not expose
BOINC's control interface can start, stop, and reconfigure work on the host; keep it on loopback (or a VPN) rather than exposing either 1043 or 31416 to the internet.
$ nmap -Pn -sV -p 1043,31416 TARGETSeen this on your network? Beige Box scans your Wi-Fi and shows every open port on every device — and its Ports tool links straight back here.
Get Beige Box →also available as JSON · Markdown
Corrections or a missing port? Reply @rimrocksystems.