Port 1615: NetBill Authorization — The ghost of Internet micropayments

Port 1615 is assigned to the NetBill Authorization Server, part of a micropayment system developed at Carnegie Mellon University in the mid-1990s. The system is long defunct, but the port assignment remains—a permanent marker of an early experiment in Internet commerce.

What NetBill Was

In the early Internet, there was a problem: credit card transaction costs made it impossible to charge less than about $10 profitably. If you wanted to sell a news article for $0.10, or a research paper for $0.50, you couldn't. The transaction fees ate everything.

NetBill tried to solve this. Developed by Marvin Sirbu and J.D. Tygar at Carnegie Mellon, it was designed to handle micropayments—transactions costing pennies or fractions of pennies. The goal was transaction costs around 1 cent for a 10-cent purchase.¹²

The system had five servers, each with its own port:

• Port 1612 — Transaction Server
• Port 1613 — Key Repository
• Port 1614 — Credential Server
• Port 1615 — Authorization Server (this port)
• Port 1616 — Product Server

The Authorization Server handled payment authorization—the moment when the system decided whether a customer could pay for a digital good. NetBill's key innovation was "atomic certified delivery": a customer paid if and only if she received her information goods intact. No money changed hands until the bits arrived.³

What Happened to NetBill

Carnegie Mellon and Mellon Bank planned a commercial trial in the first half of 1997. But NetBill never reached widespread adoption. It was absorbed by CyberCash in 1997, which was later taken over by PayPal.⁴

The system failed, but the idea didn't. Micropayments remain an unsolved problem. Port 1615 still appears in the IANA registry, assigned to a service that no longer exists.

Why This Port Matters

Port 1615 is a reminder that not every protocol succeeds. The Internet's port registry is full of optimistic projects that didn't survive—research systems, commercial experiments, standards that never caught on.

But the assignments stay. The Internet Assigned Numbers Authority (IANA) doesn't delete ports when projects die. Port 1615 will always belong to NetBill, even though no NetBill server has listened on this port in decades.

Five consecutive ports. Five pieces of a system built to solve a problem we still haven't solved. That's what you see when you look at port 1615.

Checking What's on Port 1615

If you want to see if anything is listening on port 1615 on your system:

Linux/Unix:

sudo lsof -i:1615
sudo netstat -tulpn | grep 1615

Windows:

netstat -ano | findstr 1615

You probably won't find anything. NetBill is gone. But if something is listening, it's using a port that once belonged to a system that thought you could charge a penny for a news article.⁵

The Registered Port Range

Port 1615 sits in the registered port range (1024-49151). These ports are assigned by IANA to specific services upon request. Unlike well-known ports (0-1023), registered ports don't require special privileges to bind to, which made them suitable for user applications like NetBill.

Many registered ports, like 1615, belong to services that are no longer active. The registry is an archaeological record of the Internet's evolution—every protocol someone thought mattered enough to request a port for.