Security
SSH
SSH is widely used to provide secure login access to servers. It's end-to-end encrypted, so regardless of client encryption or mode, the tunnel from localhost.run back to your app is fully encrypted.
Verifying our host keys
OpenSSH identifies servers by their host key. The first time you connect it prints the server's fingerprint and asks you to confirm it. Check that fingerprint against either of the two sources below before accepting.
Automatic verification with DNSSEC
If your local DNS resolver validates DNSSEC, OpenSSH can verify our host key against signed SSHFP DNS records on its own. Add the option to your command:
ssh -o VerifyHostKeyDNS=yes -R 80:localhost:8080 localhost.runOr set it once for every connection in your OpenSSH config (~/.ssh/config):
Host localhost.run
VerifyHostKeyDNS yesWhen the record is present and its DNSSEC signature checks out, OpenSSH accepts the key without prompting. If your resolver doesn't validate DNSSEC it falls back to the usual prompt, so verify manually.
Manual verification
Compare the fingerprint OpenSSH shows you against the matching key type:
| Key type | Fingerprint |
|---|---|
| ED25519 | SHA256:pG6qrBxubYfWa1Zadu/V0NUgjEDiBds/7e2xzte/QNM |
| RSA | SHA256:FV8IMJ4IYjYUTnd6on7PqbRjaZf4c1EhhEBgeUdE94I |
Both are also published as DNSSEC-signed SSHFP records — look them up yourself with dig +dnssec SSHFP localhost.run; the SHA-256 records decode to the fingerprints above.
HTTPS
HTTP is unencrypted, so apps should demand HTTPS. localhost.run generates HTTPS endpoints for every HTTP tunnel and handles certificates and decryption.
Proxy headers that most frameworks detect automatically are added, so requiring HTTPS is usually a single setting in your app. See HTTP tunnels.
TLS passthru
Want to use your own certificates? In TLS passthru mode localhost.run doesn't decrypt your traffic — it passes it as-is down your encrypted tunnel and your app handles decryption.