Port 1495: cvc — A registered port whose purpose time forgot

Port 1495 sits in the registered ports range (1024-49151) with an official assignment to a service called "cvc." But here's the strange part: nobody seems to know what "cvc" actually stands for anymore.

What Range This Port Belongs To

Port 1495 is a registered port. The port number space is divided into three ranges:

• Well-known ports (0-1023) — Reserved for system services, require root privileges
• Registered ports (1024-49151) — Assigned by IANA for specific services upon request
• Dynamic/ephemeral ports (49152-65535) — Used temporarily by client applications

Registered ports like 1495 are officially assigned but don't carry the same weight as well-known ports. Applications don't need special privileges to use them, and the same port number often gets reused by different services over the years.

The Official Registration

According to IANA's port registry¹, port 1495 is assigned to "cvc" for both TCP and UDP. That's all the registry says—just three letters and a port number.

The protocol documentation that would explain what "cvc" does, who created it, and why it needed a registered port? That knowledge has been lost to time. The registration remains, but the story behind it has faded.

Known Unofficial Uses

Over the years, port 1495 has appeared in various contexts:

Oracle Web Cache — Some sources associate port 1495 with Oracle Web Cache administration, though Oracle's official documentation doesn't specifically list 1495 as a default port²³. Oracle Web Cache uses multiple configurable ports for administration, invalidation, and statistics monitoring.

Historical malware — Older malware databases flagged port 1495 as being used by variants of the Gaobot worm family for backdoor access⁴. This doesn't mean the port itself is dangerous—just that malware, like any software, needs to listen somewhere.

Why Unassigned and Obscure Ports Matter

The Internet has 65,535 port numbers. Many registered ports have clear, active purposes—port 3306 for MySQL, port 5432 for PostgreSQL. But many others, like 1495, exist in a strange limbo.

They're officially assigned, so they appear in every port registry and scanning tool. They show up in security documentation and firewall rules. But the original service is gone, the company that requested it may no longer exist, and the documentation has been lost.

These ghost registrations tell a story about the Internet's history. In the 1990s and early 2000s, companies and developers requested port assignments for protocols that seemed important at the time. Some thrived. Some died quietly. The registry remembers them all.

Checking What's Using Port 1495

If you see port 1495 open on your system, here's how to find out what's actually using it:

On Linux/Mac:

# See what's listening on port 1495
sudo lsof -i :1495

# Or using netstat
sudo netstat -tulpn | grep 1495

On Windows:

# See what's using port 1495
netstat -ano | findstr :1495

# Find the process name
tasklist | findstr <PID>

The answer might surprise you. It could be Oracle software using it for administration. It could be a custom application that chose 1495 because it was registered and seemed safe. It could be nothing at all.

The Nature of Registered Ports

This is what registered ports are—requests frozen in time. Someone, somewhere, once built something that needed port 1495. They filled out the IANA form. The assignment was granted. The Internet remembered.

Whether anyone still uses "cvc" for its original purpose is unknowable. The registration remains as a monument to a protocol that once mattered enough to claim a number.