We do not publish or attest host key fingerprints for ssh.railway.com. The endpoint is served by multiple hosts, each with its own key, and those keys rotate without notice, so the fingerprint you see can differ between connections and will change over time. We do not maintain a fingerprint list, SSHFP records, or a known_hosts entry for this endpoint. How you choose to handle host key trust for it is yours to decide.

Thank you. I understand that Railway does not publish or attest host key fingerprints and that ssh.railway.com is served by multiple hosts with rotating keys.

Before deciding how to handle this for production access, could a Railway team member please confirm the recommended secure configuration for railway ssh on a new machine when no existing known_hosts entry exists?

Specifically, should users accept the host key presented by railway ssh on first connection (TOFU), or does Railway recommend another host verification mechanism?

I am specifically trying to avoid disabling host key verification globally.

Thank you.

We do not prescribe a specific host verification mechanism or a recommended procedure for handling the initial connection to ssh.railway.com. Because the endpoint is served by multiple hosts with independent, rotating keys, there is no single fingerprint to pin and no published trust anchor (no SSHFP record, no host CA, no known_hosts entry) to verify against. How you manage host key trust for this endpoint is entirely your decision.