⚠️ IMPORTANT DISCLAIMER: The tools and scripts on this site are provided "AS IS" for educational purposes.
Review destructive commands before executing. By using this site, you assume all risk and agree to our Full Terms of Service.
Fill in the host, user and key, add a bastion or port forwards, and get both a ~/.ssh/config block and the equivalent one-line ssh command. Once the config is in place, ssh myhost does the whole job.
ssh -J user@bastion user@internal-host, or in ~/.ssh/config add ProxyJump bastion under the internal host’s entry. Your key stays on your machine; the bastion only forwards the connection, which is safer than agent forwarding.
Local forwarding (-L 8080:db.internal:5432) opens a port on your machine that leads to a service reachable from the server, for example a database behind a firewall. Remote forwarding (-R 9000:localhost:3000) opens a port on the server that leads back to your machine.
ssh -D 1080 -N user@host starts a SOCKS5 proxy on local port 1080; point a browser or curl --socks5-hostname localhost:1080 at it and traffic leaves from the server. -N means no remote command, just the tunnel.
Add ServerAliveInterval 60 and ServerAliveCountMax 3 to the host entry. The client then sends a keep-alive every minute, which stops firewalls and NAT routers from closing quiet connections.
Connection sharing: ControlMaster auto, ControlPath ~/.ssh/cm-%r@%h:%p and ControlPersist 10m. New sessions, scp and git over SSH then start instantly, without logging in again.
Related tools: SSH Doctor · User & sudo Builder · All tools A–Z
Most tools run entirely in your browser. Tools marked 📡 contact outside services, as listed in the Privacy Policy. Review commands before you run them; see the Terms.