How do I secure Jupyter?

Never expose Jupyter directly. Reach it over an SSH tunnel instead: `ssh -L 8888:localhost:8888 user@your-server` and keep :8888 firewalled (`sudo ufw deny 8888`).

← what I check

EXPOSURE Jupyter
SEVERITY CRITICAL
PROBE GET :8888/api/status

CRITICAL

Is your Jupyter exposed?

Q: How many Jupyter instances are exposed?

2,295 Jupyter instances are reachable in the Shodan index (source: Shodan count · `http.title:"Jupyter Notebook","JupyterLab"`, 2026-08); that is a fingerprint match, not a verified zero-auth count.

An open notebook server is a terminal on your machine. Bots hijack these constantly.

Scan a host you own → Fix card Census

Why it matters

An open Jupyter server is a terminal on your machine for anyone who finds it. Bots scan for it constantly (it is one of the most hijacked services on the internet) and use it for crypto mining or as a foothold into the rest of your network.

How common is it?

2,295 Jupyter instances are reachable in the Shodan index. Fingerprint match, not a verified zero-auth count · src: Shodan count · `http.title:"Jupyter Notebook","JupyterLab"` · 2026-08

Counts are population-level, from third-party indexes and my own honeypots. I never scan the internet and this page makes no claim about any specific host.

Fix it

The full walkthrough lives on the fix card, kept current in one place:

Full fix card: jupyter-exposed →