17 karma · joined August 2, 2026
And a notice my registrar shows before registering a .in domain...
> This TLD has very strict verifiable contact requirements. You MUST use verifiable contact information or your domain may be suspended and / or deleted without warning by the registry and without refund. The registry is also extremely difficult to contact and communicate with, it's possible that you will be asked to rectify your unverifiable contact info and do so but then they will ignore you. Yes, it is pure insanity and bad enough that we took the time to add this very special warning.
> The .IN registry can suspend a domain at any time if it decides the registrant contact information does not hold up, and that means at any time: days into a brand new registration, or years into one you have renewed without incident. We have watched it happen to registrants who were confident their information was correct all along. Getting a suspended domain back means satisfying the registry on its terms, and that usually means ID verification: expect to be asked for eKYC and government issued ID matching the registrant contact. We will chase them on your behalf, but we cannot make them move, and until they have what they are asking for they tend to answer with form letters or not answer at all, on no particular timetable. If you cannot produce ID matching the registrant contact you are about to use, please pick a different extension. We would rather lose the sale than watch this happen to you.
> Please read that again before you check out. This is not a formality and it does not expire. The registry can come back at you long after the domain is registered, paid for and working.
Public Interest Registry's technical backend (run by Identity Digital) is owned by the same venture capital (Ethos Capital) that had to be stopped from buying PIR. Identity Digital alone operates at least 277 other TLDs.
So much money. It's crazy.
Would you mind emailing me? I'd love to help you get everything sorted. Address is in my bio.
Or you could let your webserver deal with the directory listing. Caddy's looks nice, is customisable too. Can't get simpler than that!
Realistically, fwknop is more likely to have a vuln than OpenSHH. Last release was two years ago and the readme dates back twelve :/ Time will tell.