Registered to Arepa Cas; in practice a spare development-server port next door to 3000.
IANA registers 3030 as arepa-cas, Arepa Cas, registered by Stuart Schaefer, with no RFC, no public specification and no implementation anyone meets today. What actually listens on 3030 is a local development server — a Node, Rails or similar app started on 3030 because 3000 was already taken — so the port carries no protocol guarantee at all. Scanners will still label it arepa-cas from /etc/services. Identify whatever is there by its banner or an HTTP request, not by the registered name.
Expose with care
Nothing standard runs here, so an open 3030 is an unidentified service — usually an unhardened dev server that was never meant to leave localhost.
$ curl -sS -D - -o /dev/null http://TARGET:3030/Seen 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.