# Verify SSH host key fingerprint for ssh.hf.space

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fverify-ssh-host-key-fingerprint-for-ssh-hf-space%2F190882%3E%5C
**Category:** Beginners\
**Created:** [October 21, 2026, 7:58pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fverify-ssh-host-key-fingerprint-for-ssh-hf-space%2F190882 "2026-10-21T19:58:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![RomanMaloev](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/romanmaloev/32/64510_2.png) [@RomanMaloev](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FRomanMaloev)%5C
**Post date:** [October 21, 2026, 7:58pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fverify-ssh-host-key-fingerprint-for-ssh-hf-space%2F190882%2F1 "2026-10-21T19:58:15Z")

</div>

Hello,

I’m trying to establish a secure SSH connection to my Space `RomanMaloev/space` to back up its SQLite database.

My SSH client displays this ED25519 host fingerprint:

`SHA256:hDOLEkms3mtv/Nkk1Nanj2qb1aHuOJWWE1nv1DfIZ5I`

Could a Hugging Face team member confirm whether this fingerprint is authentic, or point me to an official trusted source for verification?

Thank you!

---

<div class="post-metadata">

**Author:** ![nootxlm](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/nootxlm/32/63395_2.png) [@nootxlm](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fnootxlm)%5C
**Post date:** [October 21, 2026, 9:00pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fverify-ssh-host-key-fingerprint-for-ssh-hf-space%2F190882%2F2 "2026-10-21T21:00:04Z")

</div>

Don’t let any forum post settle this for you — including this one: the prompt exists so the trust decision happens off the channel you’re about to trust. What can settle it is agreement across independent paths. From a separate network just now, the key ssh.hf.space actually presents fingerprints to SHA256:hDOLEkms3mtv/Nkk1Nanj2qb1aHuOJWWE1nv1DfIZ5I — the same string your client shows. Run the same check from one more path you control (ssh-keyscan -t ed25519 ssh.hf.space | ssh-keygen -lf -) and compare character for character; if every path agrees, accept it once and let known\_hosts pin it — from then on, any change warns you loudly, which is where the real protection lives. If any read ever differs, stop and don’t connect.

---

<div class="post-metadata">

**Author:** ![RomanMaloev](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/romanmaloev/32/64510_2.png) [@RomanMaloev](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FRomanMaloev)%5C
**Post date:** [October 23, 2026, 8:13pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fverify-ssh-host-key-fingerprint-for-ssh-hf-space%2F190882%2F3 "2026-10-23T20:13:43Z")

</div>

Clear! Thank you for your support.🙏
