# WHATPORT(1043)

## NAME

port 1043 — boinc-client (BOINC Client Control) — Registered for BOINC client control, but the BOINC client actually listens on 31416 — the registration does not match the shipping software.

Protocol: TCP/UDP  
IANA registry

## DESCRIPTION

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`.

## EXPOSURE

**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.

## CHECK

```sh
nmap -Pn -sV -p 1043,31416 TARGET
```

## SEE ALSO

- docs — [BOINC — client configuration (--gui_rpc_port, gui_rpc_auth.cfg)](https://github.com/BOINC/boinc/wiki/Client-configuration) (github.com)
- source — [BOINC source repository](https://github.com/BOINC/boinc) (github.com)
- iana — [IANA Service Name and Transport Protocol Port Number Registry](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml) (iana.org)

---

HTML: <https://whatport.net/1043/> · JSON: <https://whatport.net/1043.json> · full dataset: <https://whatport.net/ports.json>