BRev Port 5000 — Flask, AirPlay and the collision
Port 5000 has an unusually crowded set of claimants: Flask’s development server defaults to it, the Docker Registry does too, and since macOS Monterey the operating system itself binds it for AirPlay Receiver. That last one produces the most confusing failure on the list — a brand-new Flask app reports the port in use on a machine where nothing is running, because the conflict is with a system service nobody installed.
On macOS the fix is a choice: turn AirPlay Receiver off in System Settings under General → AirDrop & Handoff, or run the app on another port. Worth knowing that the response you get from 5000 when AirPlay holds it is an HTTP 403 from the AirPlay service, which looks exactly like a broken application if you are not expecting it — people spend a long time debugging their routes over this.
The exposure verdict is never, and it is the standard development-server reasoning: Flask’s built-in server is documented as unsuitable for production, single-threaded, and with debug mode on it exposes the Werkzeug interactive debugger — a console that executes Python in the application’s process. A debug-mode Flask app reachable from the network is remote code execution with a friendly interface.
Port 5000 at a glance
| Field | Value | Detail |
|---|---|---|
| Port | 5000 | Registered |
| Service | Flask / UPnP / AirPlay | Flask’s dev server, Docker registry, and macOS AirPlay Receiver. (TCP) |
| Category | Dev & tooling | dev servers, build tools, admin consoles |
| Exposure | Never | Never expose to the internet |
Should port 5000 face the internet? On macOS it is already taken by AirPlay — the classic "port 5000 in use". Never expose a Flask dev server.
Bind it to localhost or a private network. Mass scanners find these within minutes of a host appearing online.
What commonly goes wrong
macOS: “Address already in use” with nothing running
AirPlay Receiver has the port. Disable it in System Settings → General → AirDrop & Handoff, or start the app elsewhere (flask run -p 5001). Confirm with lsof -i :5000 — you will see ControlCenter rather than python, which is the giveaway.
Requests return 403 with no matching route
Same cause seen from the client side: the AirPlay service is answering, not your application. Check which process holds the port before debugging routing, blueprint registration or CORS — none of those are involved.
Check port 5000 yourself
No browser can open a raw TCP socket, so no web page can honestly tell you whether this port is open on a remote host. These are the real commands, generated for port 5000 — swap example.com for the host you are actually testing.
What on this machine is holding port 5000?
sudo ss -tlnp | grep :5000Lists the listening socket and the PID/program holding it. Drop sudo and you get the socket but not the process name.
sudo lsof -i :5000The macOS answer to "address already in use". Kill it with `kill -9 <PID>` once you are sure what it is.
netstat -ano | findstr :5000The last column is the PID. Match it in Task Manager’s Details tab, or `taskkill /PID <pid> /F`.
Is port 5000 reachable on another host?
nc -vz example.com 5000"succeeded!" means the TCP handshake completed — the port is open. "Connection refused" is closed; a hang until timeout means filtered (a firewall dropped it silently).
nmap -Pn -p 5000 example.comThe only common tool that distinguishes open / closed / filtered. -Pn skips the ping sweep, so it still works against hosts that ignore ICMP.
Test-NetConnection example.com -Port 5000Read TcpTestSucceeded: True = open. It is built in — nothing to install.
telnet example.com 5000A blank screen or a banner means it connected. "Connection refused" means closed. Quit with Ctrl-] then `quit`.
curl -v --max-time 5 telnet://example.com:5000Handy when telnet is not installed: "Connected to …" proves the TCP handshake, without curl trying to speak HTTP.
No web page can tell you whether a port is open on a remote host
A browser cannot open a raw TCP socket — there is no API for it, by design. So a site that reports “port 3389 is OPEN on 203.0.113.10” is not checking from your browser; it is asking its own server to scan on your behalf. That works, but it means their server sees the host you asked about, scans from their address rather than yours, and answers a question about their network path, not yours.
We don't have a server here and won't pretend to. So this page does three honest things instead:
| Port | Proto | Service | What it is | Exposure | |
|---|---|---|---|---|---|
| 5000 | tcp | Flask / UPnP / AirPlay | Flask’s dev server, Docker registry, and macOS AirPlay Receiver.On macOS it is already taken by AirPlay — the classic "port 5000 in use". Never expose a Flask dev server. | Never | |
| 50000 | tcp | SAP / Db2 / dev alt | SAP instance ports, IBM Db2, and various dev servers.Business systems and databases; never public. | Never |
http://host:port/ and times it. A connection that is established proves a socket is open; an instant refusal usually means nothing is listening; anything else is honestly reported as “can't tell”. Each attempt gives up after 2.5s.nc -vz example.com 443
nmap -Pn -p 443 example.com
telnet example.com 443
curl -v --max-time 5 telnet://example.com:443
This page cannot answer that, and neither can any other page — from your browser. Opening a TCP connection to an arbitrary host and port is not something JavaScript is allowed to do. Every “open port checker” that gives you a green tick is running the scan on their server. Which is fine, as long as you know what you are agreeing to: they learn which host and port you were worried about, and the answer they give you is about the route from their data centre — not from the internet as your users see it.
What to do instead
Run the check from outside your own network. Copy an nmap or nc line from the card above and run it from a machine that is not behind the same router — a phone on mobile data with a terminal app, a cheap VPS, a colleague's laptop. Running it from inside the LAN tests the LAN, not the internet, and will happily say “open” while the world sees nothing.
Then check the thing that is actually blocking it, in this order: the service is bound to0.0.0.0 and not 127.0.0.1 · the host firewall (ufw, firewalld, Windows Defender Firewall) · the cloud security group or the router's port-forward rule · and finally your ISP, which commonly blocks 25, 80 and 445 on residential lines whatever you configure.
What a browser genuinely can verify
One thing: that an HTTPS service answers. If what you actually want to know is “is my site up and how fast is it”, the latency test measures real round trips to a CORS-open URL. If the name doesn't resolve, or resolves somewhere unexpected, that is a DNS problem, not a port problem — and it is the more common cause of “my port is closed” than an actual firewall.
An IP address finds the machine; a port picks which program on it gets the traffic. TCP sets up a connection first — a handshake, ordered delivery, retransmission — which is why the web, email and SSH use it. UDP just sends the packet with no handshake and no guarantee it arrives, which is why DNS, video calls and games use it: late data is worse than lost data.
That difference is why a UDP port is so much harder to test. TCP either completes a handshake or it doesn't, so a tool can tell you. A UDP service that has nothing to say to an unexpected packet stays silent — and silence looks identical to a firewall dropping it.
The three ranges
0–1023Assigned by IANA to core services. On Unix, binding one needs root (or CAP_NET_BIND_SERVICE).1024–49151Registered by vendors for their applications. Any user can bind these — which is why every dev server lives here.49152–65535Never assigned. The OS hands these out as the SOURCE port of your outgoing connections. (Linux actually uses 32768–60999 by default.)Closed is not the same as filtered
Closed means the host answered: the packet arrived, nothing is listening, and you got an immediate refusal (a TCP RST). Filtered means nothing answered at all — a firewall dropped your packet in silence, so you wait for a timeout and learn nothing. The difference matters: closed proves the host is reachable and the port is free; filtered tells you only that something between you and it is discarding traffic.nmap reports the two separately. A browser cannot distinguish them, which is why this page reports a timeout as “can't tell” rather than guessing.
The one habit worth keeping
Bind services to 127.0.0.1 instead of 0.0.0.0 unless something outside the machine genuinely needs them, and reach them over SSH or a VPN. Every database on the never-expose list above ships with that advice, and the leaks all begin the same way: a default bind address, a cloud instance with a public IP, and a scanner that found it within the hour.
The blocked-port list this page uses is the WHATWG Fetch Standard's “bad port” table — the ports every browser refuses to connect to (Chrome calls it ERR_UNSAFE_PORT). Local probing is additionally gated by Chrome's Local Network Access permission, which replaced Private Network Access and ships in Chrome 142.
FAQ
Why is port 5000 in use on my Mac?
macOS binds it for AirPlay Receiver from Monterey onwards. It is a system service, so nothing you installed appears in your process list — disable AirPlay Receiver in System Settings or move the application to a different port.
Can I run Flask on port 5000 in production?
Not with the built-in development server, which is single-threaded and explicitly not for production. Use gunicorn or uvicorn behind a reverse proxy; the port number is the least important part of that change.
What else uses port 5000?
The Docker Registry defaults to it, some UPnP implementations use it, and various .NET and Python tutorials pick it. Identify the process rather than guessing — the local commands on this page do that.