This is a static website that just displays my server's SSH public keys - some sort of manual pinning if you want to call it that way.
The reasoning behind this is that SSH clients don't know whether to trust the public keys on first connect - after the first connect the SSH client remembers the public keys in order to protect against a MITM attack. But there is no such protection for the very first connection to a SSH server. For that, the user needs to perform a manual verification of the public keys presented by the server (there's also an option to put the keys into DNS, but it isn't widely supported).
If you're connecting to my SSH server, please compare the given public keys with the ones shown below - if they do not match, do NOT connect but notify me instead.
SHA256:p/oOL/857dbDXcJM0xGjfcIizgBw3g+ERFFc58X6G3A5bitelzQ (ED25519) SHA256:OjO7iyPlkBhCFfb4Grg1YEi1xbTXGkKV01nc3RkaY7g (ECDSA) SHA256:4n7XYLQ6CnjqYpOskmbDHx4XPEXIkQ++NSImqL15Ppr4 (RSA)
MD5:cf:ce:84:3e:18:17:f0:a9:ae:3f:57:4b:03:84:10:14 (ED25519) MD5:c4:d2:1a:de:f6:72:2c:80:bb:98:17:87:60:1a:59:de (ECDSA) MD5:3f:50:d6:54:a6:da:84:91:1a:c6:b0:b5:b2:83:20:47 (RSA)
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIGJhmeRF4X6d0ch265BNsn8OhLpK453+GogiesdCSV9a ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBIX3vIEVmhWjRXf61qD7fpuBsNk42soCMjvlYiJ+n7tinPwddOxKmVe0fdqs/jtTSHMDsbL72gd+kZpQWRpmVjo= ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDphheaoV5b6MSyTjb/69zQ9C7OUG+y7aOfrwRwgG8IC8JA0tBnfLfzpvakIZDD7SXBYOq+CSsalK6GWWnXsBH43OI6bbRWLPjWCG35GyAwIz9NarHHa2InbW3akdxjj+o+DVd9cVX3jz8KKSFgF7gu3ElFUk9cWh/LoPmlPRl8YVxbD5uhbgMEku+nV9RicqzElyGyKlC3Pd9IcySTmXMTxytA4/CHxnkycsZyW20MjyL4fpgRrzstfL/600H94kHQ3sui1dmsZjeYReDMmcUZ3I2iJUDjcGjjM6Uw9JS5d3BlnFuLtH7kQhlS/jQ4IhnYako/x93SRXBMSdelBbAJ
Note: I do rotate the keys occasionally, so you may get "Host key has changed" warnings at some point. In that case, return to this page and check the new keys.