I like to use Hetzner for little static sites (this) or simple php/cgi scripts (marketing people call it FaaS, today).
Hetzner uses a fleet of web servers for their hosting and resolving their IP(s) returns someting like:
$ host www42.your-server.de
www42.your-server.de has address 167.235.121.129
www42.your-server.de has IPv6 address 2a01:4f8:1061:21b4::2
www42.your-server.de mail is handled by 10 www42.your-server.de.
If you’re using sftp to connect to your webspace (using rclone, dolphin, maybe CyberDuck WinSCP if those still exist?) then the connection is established via IPv6 (if you also have one):
$ sftp -v www42.your-server.de
debug1: OpenSSH_10.2p1 Ubuntu-2ubuntu3.8, OpenSSL 3.5.5 27 Jan 2026
debug1: Reading configuration data /home/bob/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to www42.your-server.de [2a01:4f8:1061:21b4::2] port 22.
debug1: Connection established.
debug1: no pubkey loaded from /home/bob/.ssh/id_rsa
[...]
If you (or your program) tries the username/password 5 times then you’re banned (for hours, actually). It took me a while to figure this out. The hard way.
While I don’t like my solution, it works: We keep using ipv4 (ssh config setting: AddressFamily inet), here the limits are much higher (I never ran into a ban state using ipv4):
$ cat ~/.ssh/config
Host example.com # or www42.your-server.de if you want to use the original DNS name
Hostname www42.your-server.de
User bob20d2
IdentityFile ~/.ssh/id_ed25519
ForwardAgent no
StrictHostKeyChecking yes
AddressFamily inet # use ipv4 because ipv6 seems to have a too aggressive banning
Filed under “things that should just work with ipv6 but don’t. I wish they would just default to either mandatory ssh keys or really long ssh passwords, instead.”