Port 1965: Gemini — The Internet's Quiet Room

What Runs on Port 1965

Port 1965 has no official IANA assignment. But in practice, it belongs to Gemini, a community-built Internet protocol that launched in 2019 and quietly attracted thousands of servers and readers who wanted something the modern web couldn't offer: simplicity with privacy, by design.

Gemini servers listen on TCP port 1965. The number is intentional. As the protocol specification states plainly: "the year the first crewed Gemini mission flew." Someone cared enough to encode a small piece of space history into the protocol's address.¹

What Gemini Is

Gemini sits between Gopher (1991, minimal, no encryption) and HTTP (complex, powerful, increasingly hostile to users). It doesn't try to replace either. It coexists.

A Gemini request is simple: the client opens a TLS connection, sends a URL on a single line, and the server responds with a status code, a MIME type, and content. That's it. No cookies. No headers advertising your browser version, screen size, or preferred language. No JavaScript. No way to embed tracking pixels or run fingerprinting scripts.

The document format, called Gemtext, is even simpler than Markdown. Links go on their own lines. There are no inline images. You can't make text bold mid-sentence. These aren't bugs — they're the point. The constraints make it impossible to build the surveillance-driven attention economy that the web became.

Why It Exists

In 2019, a pseudonymous developer known as Solderpunk was active in "Gopherspace," a still-living community of people publishing on the old Gopher protocol as a refuge from the commercial web.² Solderpunk wrote a series of posts wondering: what if you built something new — not as old as Gopher, not as heavy as the web?

The project was announced on June 20, 2019. That date is now Gemini's official birthday.

The protocol mandates TLS for every connection, which means Gemini is, by default, more encrypted than many parts of the actual web it's reacting against. You can't run a cleartext Gemini server. Privacy isn't optional — it's structural.

The Range This Port Lives In

Port 1965 falls in the registered port range (1024–49151). IANA manages this range, and any organization can formally apply to register a port for a service. Port 1965 has no official IANA registration.³

That's fine. The Gemini community never applied. The protocol was built outside institutions, spread by word of mouth (or rather, by hyperlinks in Gemtext), and the servers that run it are mostly personal projects — "capsules," in Gemini vocabulary — run by individuals.

How to Check What's Listening

If you want to see whether anything is running on port 1965 on a machine you control:

# On Linux/macOS — show what's listening on port 1965
ss -tlnp | grep 1965

# Or with lsof
lsof -i :1965

# Connect to a Gemini capsule directly (requires a Gemini client or openssl)
openssl s_client -connect geminiprotocol.net:1965

Standard web browsers don't speak Gemini. You need a dedicated client. Lagrange and Amfora are popular options.

Why Unassigned Ports Matter

The port space is finite. IANA's registry exists to prevent collisions — two services accidentally claiming the same port on the same machine creates chaos. But registration isn't mandatory, and the registered range is vast enough that informal conventions take hold.

Port 1965 is a good example of how that works in practice. No committee assigned it. No RFC formalized it. A developer picked a number with a story, the community adopted it, and now tens of thousands of Gemini capsules listen on the same port by informal consensus. It works because everyone agrees it works.

The port will probably never get official IANA status. Gemini has no interest in becoming an institution.