Port 1634 is a registered port assigned to loaprobe (Log On America Probe), a service from the 1990s that no longer exists. The company that requested this port has been permanently closed for decades, yet the IANA registry preserves the assignment.
What is Port 1634?
Port 1634 is a registered port in the range 1024-49151. These ports are assigned by IANA (Internet Assigned Numbers Authority) to specific services upon request by companies or organizations.1
The official assignment:
- Service name: loaprobe
- Description: Log On America Probe
- Protocol: TCP and UDP
- Registered by: Log On America, Inc.
The Story Behind the Port
Log On America was incorporated in Rhode Island in 1992 as an online and Internet services provider.2 During the early commercial Internet era, it competed alongside better-known services like AOL, CompuServe, and Prodigy.
The company registered port 1634 for its "probe" service—likely a diagnostic or monitoring tool used to check the status of Log On America systems or client connections. The exact technical details of how loaprobe worked have been lost to time.
Log On America is now permanently closed. The company is gone, the service is gone, but port 1634 remains registered in the IANA database—a small monument to a forgotten piece of Internet history.
Why This Port Matters
Port 1634 tells a larger story about how the Internet's infrastructure works:
Port assignments are permanent. Once IANA assigns a port to a service, that assignment typically remains even if the service disappears. The registry becomes an archaeological record of Internet history.
Thousands of registered ports are unused. Many registered ports belong to defunct companies, abandoned protocols, or services that never gained traction. These "ghost ports" sit in the registry, theoretically available but practically empty.
New services can't claim them. Even though no traffic flows through port 1634 for its original purpose, another company can't simply take over the assignment. The port remains associated with loaprobe.
This is both a strength and a limitation of the port registration system. It provides stability and prevents conflicts, but it also means the registry accumulates cruft—assignments that no longer serve any active purpose.
What Might Be Using Port 1634 Today
While the official loaprobe service is dead, port 1634 isn't necessarily silent:
Unofficial uses: Some applications or services might use port 1634 for unrelated purposes. Since it's in the registered range (not well-known), it's less likely to conflict with common services, making it attractive for custom applications.
Malware or botnets: Security researchers sometimes observe malicious traffic on obscure registered ports, though there's no specific widespread threat associated with 1634.
Private applications: Network administrators might configure internal services to use port 1634, unaware of or unconcerned with its official assignment.
Nothing at all: Most likely, this port sees no traffic on most networks. It's simply there, waiting for a service that will never return.
How to Check What's Using Port 1634
If you want to see whether anything is listening on port 1634 on your system:
On Linux or macOS:
On Windows:
If you see nothing, that's the expected result. Port 1634 is a ghost—present in the registry, absent from reality.
The Registered Port Range
Port 1634 falls within the registered ports (1024-49151). This middle range of the port number space is where organizations can request assignments for specific services.
Unlike well-known ports (0-1023) which require root privileges to bind on Unix-like systems, registered ports can be used by regular user applications. Unlike dynamic/ephemeral ports (49152-65535) which are meant for temporary use, registered ports are supposed to identify specific services permanently.
The registered range is where you find:
- Proprietary business applications
- Database systems (MySQL on 3306, PostgreSQL on 5432)
- Game servers and custom protocols
- And ghosts like loaprobe on 1634
Security Considerations
Port 1634 poses no inherent security risk since no legitimate service actively uses it. However:
Monitor for unexpected activity. If you see traffic on port 1634, investigate it. Since the legitimate service is defunct, any activity is either a custom application you should know about, or potentially malicious.
Don't assume obscure means safe. Attackers sometimes use unusual registered ports hoping administrators won't notice. Port 1634's obscurity doesn't protect you—firewall rules and monitoring still apply.
Close unused ports. If you're not intentionally running anything on 1634, it should be closed by default (which it likely is unless you've explicitly opened it).
The Archaeology of the Internet
Every port in the registry tells a story. Some ports carry the weight of billions of daily connections. Others, like 1634, carry only the weight of memory.
Log On America wanted to be part of the Internet's future. They registered a port, built their service, and joined the great experiment of connecting the world. The company failed. The service vanished. The users moved on.
But port 1634 remains. In the IANA registry, loaprobe still exists. It's a marker of something that once mattered to someone—a small claim on Internet infrastructure that outlasted the claimant.
This is what happens to abandoned ports. They don't get recycled or reassigned. They just sit there, waiting. The Internet doesn't forget its assignments, even when everyone else has.
Ця сторінка була корисною?