Skip to content
Verify official SSH gateway host-key fingerprint
ritikkh03-ai
OP

a month ago

Hi Railway Team,

Could you please confirm the official SSH gateway host-key fingerprint for ssh.railway.com?

My Mac received the following:

Algorithm: ED25519

Fingerprint: SHA256:+S1xg92FrnHz6pY3bpkmh1OGtWQGNANXilPzlxA7B1g

I want to independently verify the gateway's identity before performing production PostgreSQL TLS diagnostics.

Can you confirm whether this fingerprint is authentic?

Thank you.

Solved

3 Replies

Railway
BOT

a month ago

We don't confirm or deny individual host-key fingerprints for ssh.railway.com, and we don't publish a fingerprint list or known_hosts entry for it. The endpoint is served by multiple hosts, each with its own key, and those hosts change at any time without notice. A different fingerprint between connections, or over time, is expected and is not something to report each time.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway

We don't confirm or deny individual host-key fingerprints for `ssh.railway.com`, and we don't publish a fingerprint list or known_hosts entry for it. The endpoint is served by multiple hosts, each with its own key, and those hosts change at any time without notice. A different fingerprint between connections, or over time, is expected and is not something to report each time.

ritikkh03-ai
OP

a month ago

Hi Railway Team,

Thank you for the automated response.

I understand that ssh.railway.com uses multiple hosts with rotating SSH host keys and that Railway does not publish or confirm individual fingerprints.

My concern is how to securely authenticate the SSH gateway before accessing a production PostgreSQL service.

Could a Railway engineer please clarify:

  1. What is Railway's officially recommended method for verifying the identity of ssh.railway.com when connecting through the Railway CLI?
  2. Does Railway recommend accepting SSH host keys on first use (TOFU), or is there a supported alternative such as SSH host certificates or a trusted known-hosts mechanism?
  3. How should customers safely handle unexpected SSH host-key changes?

I'm implementing encrypted, independently recoverable PostgreSQL backups and want to follow Railway's recommended security practices.

A response from a Railway engineer or a link to official documentation would be appreciated.

Thank you!


Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

We don't have a host-key verification mechanism for ssh.railway.com to recommend. We don't publish fingerprints, a known_hosts entry, SSHFP records, or a host CA, and none of those are planned.

We also don't have a recommended procedure for host-key trust on this endpoint, whether that's TOFU or handling a key change. Its host keys can change at any time without notice, and different connections can present different keys. A changed fingerprint is expected, and pinning one will break. How you handle host-key trust for this endpoint is your decision.


Status changed to Awaiting User Response Railway • about 1 month ago


Status changed to Solved ritikkh03-ai • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...