Gopher — the pre-web menu protocol, still served by a small but real community of hosts.
RFC 1436 defines Gopher as a request/response protocol where the client sends a selector string followed by CRLF and the server returns either a file or a tab-delimited menu, one item per line, each carrying a type character, display string, selector, host and port. It has no cookies, no scripting, and no session state, which is much of its appeal to the people still running it. Floodgap's public server on gopher.floodgap.com has been up since 1999 and is the usual entry point. Servers such as Gophernicus keep the protocol maintained on modern systems.
Fine to expose
A read-only, unauthenticated public publishing protocol with no credentials to leak; the risk is server-side path handling, not the protocol.
$ printf '\r\n' | nc -v gopher.floodgap.com 70 | head -20Seen 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.