We can't confirm or deny a specific fingerprint for ssh.railway.com. The endpoint is served by multiple hosts, each with its own host key, and those keys change at any time without notice.

We don't publish a fingerprint list, known_hosts entry, or SSHFP record for it. Seeing a different fingerprint on a later connection, or a "host identification has changed" warning, is expected and not a sign that anything is wrong.

Thank you for your response.

I understand that Railway uses multiple SSH host keys and does not publish their fingerprints.

However, I need to establish a secure SSH connection to my private QA environment.

Could a Railway engineer confirm the recommended secure procedure for establishing a first SSH connection when the host fingerprint cannot be independently verified?

Is there an official alternative to trust-on-first-use authentication?

We don't have an official alternative to trust-on-first-use for ssh.railway.com, and we don't publish a recommended procedure for verifying its host key on first connection. The endpoint is served by multiple hosts, and each one has its own key that can change at any time without notice. How you handle host key trust for this endpoint is up to you.