What This Port Is
Port 3018 sits in the registered port range — the band from 1024 to 49151 that IANA manages for services that have formally requested a port assignment. Unlike the well-known ports below 1024 (where HTTP lives at 80, SSH at 22, DNS at 53), registered ports don't require elevated system privileges to use. Anyone can listen on 3018. But not just anyone gets to claim it.
IANA's registry lists port 3018 as assigned to srvc-registry, described simply as "Service Registry," attributed to a contact named Mark Killgore on both TCP and UDP.1
That's where the trail goes cold.
The Ghost Registration Problem
There are thousands of ports in the registered range. Some of them host essential services used by millions of systems daily. Others are like port 3018: assigned, named, and then... nothing. No RFC. No open-source implementation. No documentation. No software that announces itself on this port.
This happens for several reasons:
- A developer registers a port for a proprietary service that gets abandoned, pivoted away from, or never ships
- An internal tool claims a port officially but never becomes a public product
- A company registers preemptively and then builds something different
Port 3018's registration for "Service Registry" is plausible in concept — service registries (systems where microservices announce themselves so other services can find them) are a real and important category of infrastructure software. But the popular implementations — Consul, Netflix Eureka, Apache ZooKeeper, etcd — use their own ports and never had anything to do with 3018.2
Whatever srvc-registry was meant to be, it left no public trace.
What's Actually on Port 3018 on Your System
If you see traffic or an open listener on port 3018, it has nothing to do with the IANA registration. That registration is a historical claim, not a guarantee of what software uses the port in practice. Any application can bind to 3018.
To check what's listening:
macOS / Linux:
Linux (alternative):
Windows:
The output will show you the process ID and name of whatever has claimed the port. Common culprits for activity on obscure ports: development servers, local proxies, database management tools, or software that picked the port semi-arbitrarily.
Why Registered Ports Matter
The registered range exists to prevent collisions. If every developer picked port numbers randomly, two pieces of software installed on the same machine would constantly fight over the same ports. IANA's registry is the record of who agreed to use what.
It's not perfect. The registry contains abandoned claims, duplicates, and ports that no living software uses. But it's the shared agreement that makes "run this on its default port" mean anything at all.
Port 3018's registration is technically valid. In practice, if you encounter traffic here, you're dealing with something local to your environment — not a service with a public specification you can look up.
Frequently Asked Questions
Czy ta strona była pomocna?