Port 1891: ChildKey Notification — A registered port for software that vanished

Port 1891 is a registered port. IANA lists it as childkey-notif — the notification channel for something called ChildKey, apparently a parental control or child monitoring system. Port 1892 sits next to it as childkey-ctrl, the control channel.

That's nearly everything that's known about it.

The software has vanished. The company is untraceable. No documentation, no user forums, no GitHub repositories, no press releases. Whatever ChildKey was, it registered its ports with IANA, built its system, and then disappeared — leaving behind two port numbers and a service name as the only evidence it ever existed.

What the Registration Means

Port 1891 sits in the registered port range (1024-49151). This range is administered by IANA, and anyone can apply to register a port for their service.¹ Registration doesn't require the software to be widely used, open source, or even still alive. It just requires submitting the paperwork.

The registered range exists to prevent port collisions — if two applications independently chose the same port, they'd conflict whenever both were installed on the same machine. Registration is the system's way of saying "this number is spoken for."

So port 1891 is spoken for. By something that no longer answers.

What Likely Ran Here

Based on the port pair (1891 notification, 1892 control), ChildKey was probably a client-server parental monitoring application. The pattern is common in monitoring software:

• A notification port receives alerts, events, or status updates from the monitored device
• A control port sends commands — block this site, set this time limit, restrict this application

The child's device would have run an agent listening on or connecting through these ports. The parent's console would have communicated back. This is standard architecture for any monitoring system that needs real-time communication between two endpoints.

If You See This Port Active

If port 1891 shows up on your network today, it isn't ChildKey — that software is gone. More likely explanations:

• An application chose this port informally, unaware of the registration
• A game, custom service, or development tool is using it
• Something is scanning your network and happened to probe this port

To see what's actually listening:

On Linux/macOS:

# Show what process owns port 1891
sudo lsof -i :1891

# Alternative with ss
sudo ss -tlnp | grep 1891

On Windows:

netstat -ano | findstr :1891
tasklist | findstr <PID>

The Quiet Register

The IANA port registry contains thousands of entries like this one — ports claimed by software that has since gone quiet. Some were commercial products that failed. Some were internal tools registered by companies that were later acquired or shut down. Some were academic projects. The registry doesn't expire entries or remove them when the software dies.

In a way, these ghost registrations serve a purpose: they keep other software from accidentally squatting on a number that might still mean something to someone running an old system somewhere. The registered range is a historical record as much as a live directory.

Port 1891 has a name. It has a neighbor at 1892. And somewhere, on a machine that probably hasn't been turned on in years, there might still be a copy of ChildKey that once used it.