185.104.35.1

This address is yours, and it is answering — this page is the proof. Nothing has been deployed to it yet, so it is still showing ours. Here is how it stops being ours.

Put your site on it

From your own machine, in the directory your site is in:

rsync -az ./ 185.104.35.1:              # mirror this directory
sftp 185.104.35.1                       # or upload interactively
git push 185.104.35.1:site HEAD:main    # or push a branch

Each upload lands as one complete version and swaps in at once, so a connection that drops halfway changes nothing and nobody ever sees a half-uploaded site. The way back is one word:

ssh 185.104.35.1 versions
ssh 185.104.35.1 rollback

And the rest of it

Your own name on it

domain add example.com — point its A record here first. The certificate is issued on the first request and renews itself.

Reverse DNS you set yourself

ptr mail.example.com — forward-confirmed, which is what mail servers check and what most hosts will not hand over.

The address, on a machine of your own

wireguard routes all of it home through one outbound tunnel — every port, straight through carrier NAT, no port to forward. wireguard off hands it back.

Or no web page at all

web off and the address answers nothing, this page included. Nothing is deleted; web on brings it back.

Everything runs as ssh 185.104.35.1 <command>. help lists the lot, and the list keeps growing.

Your key is the account — the user name is ignored. Register a second one with keys add while you still have the first: there is no password reset and no email recovery, so a pod whose keys are all lost cannot be reopened by anyone, us included.