Port 3639: xap-ha — The Home Automation Protocol That Broadcast Everything

What This Port Does

Port 3639 is assigned to xap-ha — the xAP (eXtensible Automation Protocol) home automation protocol. xAP was designed to solve an early smart home problem: your Caller ID system, your alarm, your lighting controller, and your heating system were all made by different companies that had no interest in talking to each other. xAP gave them a common language.

Every xAP message goes out as a UDP broadcast on port 3639. Every device on the local network receives it. Every device decides for itself whether to act on it. There's no central authority, no negotiation — just a continuous conversation everyone can hear.

The Hub Problem

UDP has a constraint: only one application can bind a port at a time. If you want to run three xAP applications on the same machine — say, a heating controller, a logging daemon, and a lighting bridge — only one of them can listen on port 3639.

xAP solves this with a required hub process. The hub binds port 3639, receives all incoming broadcasts, and redistributes them to each local application over high-numbered ephemeral ports. It's a small piece of infrastructure that makes the whole ecosystem work on a single machine.

Who Built It and When

xAP emerged from the home automation enthusiast community in the early 2000s, co-developed by contributors including Mark Harrison. IANA registered the port assignment in November 2002.¹ The protocol was explicitly designed to be minimal — easy to implement in anything from a PC to an embedded microcontroller, over Ethernet, Wi-Fi, or serial connections.²

The protocol never became a mainstream standard. Zigbee, Z-Wave, and eventually Matter absorbed the home automation market. But xAP represents a genuine engineering philosophy: open, extensible, and deliberately simple, because the goal was interoperability, not vendor lock-in.

What Range This Port Belongs To

Port 3639 sits in the registered ports range (1024–49151). IANA maintains this registry so that services can claim a consistent port number without conflicting with each other. Unlike the well-known ports below 1024 (which require root/administrator privileges to bind on Unix systems), registered ports can be used by any process.

An IANA assignment here doesn't mean the service is widely deployed — it means someone registered the number to prevent collisions. xap-ha has a legitimate claim to 3639; most modern systems will never see traffic on it.

What to Do If You See Traffic on Port 3639

On a modern network, unexpected traffic on port 3639 is almost certainly one of two things:

1. A home automation system using xAP (rare but legitimate)
2. Something that chose this port arbitrarily (applications sometimes pick registered-but-quiet ports for custom protocols)

To check what's listening on your machine:

# macOS / Linux
sudo lsof -i :3639
sudo ss -tulpn | grep 3639

# Windows
netstat -ano | findstr :3639

To capture live traffic on the port:

sudo tcpdump -i any udp port 3639

xAP messages are plain text — if you see human-readable key/value pairs in the capture, it's probably genuine xAP traffic.