BRev Port 8888 — Jupyter and HTTP alternates
Port 8888 is best known as the Jupyter Notebook and JupyterLab default, and the security consequence is worth stating plainly: a notebook executes arbitrary code on the machine that runs it, as the user that started it, with a web UI. It is a remote shell whose interface happens to render plots. Anyone who can open the page can read the filesystem, reach anything the host can reach, and run whatever they like.
The token in the startup URL — the long hex string after ?token= — is the entire authentication for a default installation. Copy the URL without it and you get a login prompt; publish the port without setting a password, and on many older configurations there is nothing to prompt for. Exposed Jupyter instances have been catalogued repeatedly and are actively hunted, most commonly to install cryptocurrency miners on machines that were chosen precisely because they have GPUs.
It is also a generic alternate HTTP port, used by proxies (mitmproxy and Fiddler among them), various dashboards and plenty of container images, so a listener on 8888 is not necessarily Jupyter. The remote-access rule is the same either way: bind it to localhost and reach it through an SSH tunnel — ssh -L 8888:localhost:8888 user@host — which is also how you use a remote GPU box safely.
Port 8888 at a glance
| Field | Value | Detail |
|---|---|---|
| Port | 8888 | Registered |
| Service | Jupyter / HTTP alt | Jupyter Notebook default, and a common alternate HTTP port. (TCP) |
| Category | Dev & tooling | dev servers, build tools, admin consoles |
| Exposure | Never | Never expose to the internet |
Should port 8888 face the internet? A notebook is an interactive shell in a browser; token-less instances get mined.
Bind it to localhost or a private network. Mass scanners find these within minutes of a host appearing online.
What commonly goes wrong
“Invalid credentials” or an endless token prompt
The token is per-server-process and regenerates on restart, so a bookmarked URL stops working. jupyter server list prints the running servers with their current tokens. For anything long-lived, set a password instead (jupyter server password) so the URL stops carrying the secret.
The port is in use, or the notebook opened on 8889
Jupyter increments to the next free port when 8888 is taken, which is usually a previous kernel that never exited or a second JupyterLab. That is why people end up with three notebook servers and no idea which is which — list them with jupyter server list and stop the ones you are not using.
Check port 8888 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 8888 — swap example.com for the host you are actually testing.
What on this machine is holding port 8888?
sudo ss -tlnp | grep :8888Lists the listening socket and the PID/program holding it. Drop sudo and you get the socket but not the process name.
sudo lsof -i :8888The macOS answer to "address already in use". Kill it with `kill -9 <PID>` once you are sure what it is.
netstat -ano | findstr :8888The last column is the PID. Match it in Task Manager’s Details tab, or `taskkill /PID <pid> /F`.
Is port 8888 reachable on another host?
nc -vz example.com 8888"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 8888 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 8888Read TcpTestSucceeded: True = open. It is built in — nothing to install.
telnet example.com 8888A 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:8888Handy 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 | |
|---|---|---|---|---|---|
| 8888 | tcp | Jupyter / HTTP alt | Jupyter Notebook default, and a common alternate HTTP port.A notebook is an interactive shell in a browser; token-less instances get mined. | 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 expose Jupyter on port 8888?
No. It is arbitrary code execution behind a web page, and exposed instances are actively scanned for and mined. Bind to 127.0.0.1 and use an SSH tunnel, or put it behind a real authenticating proxy — JupyterHub exists for the multi-user case.
What is the token in the Jupyter URL?
The default authentication. It is generated per server process, so it changes on every restart and any bookmark without it hits a login prompt. Setting a password is the better answer for a server you keep running.
Something is on 8888 and it is not Jupyter
Likely an intercepting proxy (mitmproxy, Fiddler), a container publishing a dashboard, or another alternate HTTP service. Identify the process with the local commands on this page before assuming anything about it.