Give localhost a public https URL
Free during the beta with a registered account. Sign up, create an API key, and run one command.
Get a tunnel URLA RevSheller tunnel gives a port on your machine a public https URL. A client on your machine opens an outbound connection, and requests to the URL are forwarded down it to a port on localhost. This page covers what works, what is specific to RevSheller, and what a tunnel does not cover.
The one-command version
With a web server running on port 3000 and an API key from your account page:
(curl -fsSL https://revsheller.com/tn.sh || wget -qO- https://revsheller.com/tn.sh) | RSH_API_KEY=rsh_YOUR_KEY sh -s -- http 3000
On Windows PowerShell:
$env:RSH_API_KEY="rsh_YOUR_KEY"; & ([scriptblock]::Create((irm https://revsheller.com/tn.ps1))) http 3000
The client prints a URL like https://tn-k3v9q2m7xa.revshell.org and then one log line per request. Ctrl-C closes the tunnel and deletes it. Random URLs are never reused.
If you would rather not pipe a script into a shell, read it first: curl -fsSL https://revsheller.com/tn.sh -o tn.sh. It is about fifty lines that download the client binary for your OS, check its SHA-256 and run it. The binaries are also linked directly from the API docs. With Node.js 22 or newer you can use the JavaScript build instead: curl -fsSL https://revsheller.com/tn | node - http 3000.
What works
- A public https URL for a local port, with TLS handled at the edge, so your local server can stay plain http.
- WebSockets are forwarded, so live reload and socket-based apps can work through the tunnel.
- Reconnects. If your network drops, the client reconnects to the same tunnel with backoff.
- A browser warning page. Browsers see a short notice before the app loads. Webhooks and API clients skip it.
What is specific to RevSheller
- No agent to install. The one-liner fetches a small native client for your OS, checks it against a pinned SHA-256 and caches it. There is no sign-up step in the client, no package manager and no runtime to install.
- Its own domain. Tunnels live on
revshell.org, separate fromrevsheller.comwhere your account lives. The app's cookies and API keys never share a site with tunneled apps. - The key stays out of argv. The client refuses an API key passed as a command-line argument. It reads
RSH_API_KEY, a saved config (--save), or prompts on the terminal with input hidden. - Agents can create tunnels. The MCP server has
tunnel_create,tunnel_listandtunnel_delete. An agent can set up a tunnel and hand you the command to run, without ever seeing your key. - A shell relay in the same account. RevSheller also runs a browser-based reverse shell relay for CTFs and labs. You can ignore it if you only need tunnels.
What a tunnel does not cover
- You need TCP or TLS tunnels. RevSheller forwards HTTP and WebSockets only.
- You need your own domain or a URL that never changes. During the beta, tunnels get a random
tn-name and last up to 8 hours. Reserved names are planned for paid plans after the beta. Bringing your own domain is not supported. - You rely on a local request inspector or replay. The RevSheller client logs one line per request (or JSON lines with
--log json). It has no inspection UI. - You are serving production traffic. RevSheller tunnels are in beta and meant for development, testing and demos.
Limits during the beta
Every registered account gets the same tunnel limits during the beta:
| Tunnels open at once | 2 |
| Traffic per month | 10 GiB (requests, responses and WebSocket messages) |
| Tunnel lifetime | Up to 8 hours, then the client opens a new tunnel with a new URL |
| Requests per minute, per tunnel | 600 |
| Request body size | 25 MB |
| Concurrent requests, per tunnel | 100 |
| Open visitor WebSockets, per tunnel | 20 |
The planned limits for each plan after the beta are on the pricing page.
Security notes
- Only registered accounts can open tunnels, and each tunnel is tied to its owner. Reported tunnels can be suspended. See Report abuse.
- Tunnel hosts answer
/robots.txtwithDisallow: /and sendX-Robots-Tag: noindex, so search engines don't index your dev server. - Your app receives the visitor's IP in
X-Forwarded-For. - Cookie isolation between tunnels is not complete yet.
revshell.orgis not yet on the Public Suffix List, so JavaScript on one tunnel can set a cookie forDomain=revshell.orgthat other tunnels' apps then receive. Cookies your server sets with a Domain attribute are made host-only, but don't rely on cookie isolation between tunnels for anything sensitive yet.
FAQ
Do I need to install anything?
No. The one-line command fetches a small native client for macOS, Linux or Windows, checks it against a pinned SHA-256 and caches it. No runtime or package manager is needed.
Does it support TCP tunnels?
No, HTTP and WebSockets only.
Can I keep the same URL?
Not during the beta. A tunnel keeps its URL while it is open, up to 8 hours. Reserved names are planned for paid plans.
Is it free?
Free during the beta for registered accounts. Paid plans are planned for after the beta and are not final. See pricing.