BRev Port 8000 — dev servers
Port 8000 is where a handful of very common development servers land: Django’s manage.py runserver, python3 -m http.server, php -S in many tutorials, and a long tail of Node and Go examples. It is not a registered service — it is simply another round number above 1024, which is why several tools chose it independently and why conflicts on a busy machine are routine.
The one-line file server deserves its own warning. python3 -m http.server serves the directory it was started in, recursively, with directory listings and no authentication. Started in a home directory or a project root it publishes SSH keys, .env files, .git history and cloud credentials to anyone who can reach the port. It binds all interfaces by default in Python 3, so on a café or office network that means everyone on the segment — the -b 127.0.0.1 argument is the one that matters.
Django’s runserver has its own sharp edge: it is explicitly not a production server, and with DEBUG on, an unhandled exception renders a full traceback including local variables and settings. The exposure verdict here is never, and it is about that combination — a debug-mode application with verbose errors, no hardening and often a database connection, listening on a port people forget is open.
Port 8000 at a glance
| Field | Value | Detail |
|---|---|---|
| Port | 8000 | Registered |
| Service | HTTP alt / dev server | Django, `python -m http.server`, and countless others. (TCP) |
| Category | Dev & tooling | dev servers, build tools, admin consoles |
| Exposure | Never | Never expose to the internet |
Should port 8000 face the internet? The one-line file server exposes your working directory to the world.
Bind it to localhost or a private network. Mass scanners find these within minutes of a host appearing online.
What commonly goes wrong
“That port is already in use” from Django
A previous runserver did not exit — its autoreloader spawns a child process, so killing the terminal sometimes leaves the child holding the socket. Find the PID with the local command on this page and kill it, rather than starting on 8001 and forgetting which is which. On macOS also check whether another tool grabbed the port first.
You served a directory and now regret it
Assume everything under that directory was readable while the server ran, including dotfiles — http.server does not hide them. Rotate anything sensitive that was in scope: .env values, API keys, SSH private keys, cloud credential files. Then restart with -b 127.0.0.1 and a directory that contains only what you meant to share.
Check port 8000 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 8000 — swap example.com for the host you are actually testing.
What on this machine is holding port 8000?
sudo ss -tlnp | grep :8000Lists the listening socket and the PID/program holding it. Drop sudo and you get the socket but not the process name.
sudo lsof -i :8000The macOS answer to "address already in use". Kill it with `kill -9 <PID>` once you are sure what it is.
netstat -ano | findstr :8000The last column is the PID. Match it in Task Manager’s Details tab, or `taskkill /PID <pid> /F`.
Is port 8000 reachable on another host?
nc -vz example.com 8000"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 8000 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 8000Read TcpTestSucceeded: True = open. It is built in — nothing to install.
telnet example.com 8000A 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:8000Handy 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 | |
|---|---|---|---|---|---|
| 8000 | tcp | HTTP alt / dev server | Django, `python -m http.server`, and countless others.The one-line file server exposes your working directory to the world. | 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
Is it safe to run python -m http.server?
On localhost, yes. Bound to all interfaces it exposes the entire working directory tree, with listings, to everyone who can reach the machine — and it defaults to all interfaces. Always pass -b 127.0.0.1 unless you deliberately want the LAN to have it.
Can I run Django on port 8000 in production?
Not with runserver, which is single-threaded, unhardened and documented as unsuitable. Production means a WSGI/ASGI server such as gunicorn or uvicorn behind a reverse proxy handling TLS — the port number is the least important part of the change.
What is the difference between port 8000 and 8080?
Convention only. Both are unprivileged ports used for HTTP; 8000 skews towards Python tooling and 8080 towards Java application servers and proxies. Neither is special to any protocol.