.iamthat is the root pilot.
We delegated the real Handshake TLD .iamthat to a
Handout-managed server and confirmed it resolves through HNS-aware
tooling.
Live LearnHNS revival project
Handout helps a Handshake TLD become a working website.
Owning a Handshake name is only the first step. Handout is the open-source path we are reviving so a TLD owner can publish authoritative DNS, DNSSEC, DANE/TLSA, and web hosting without turning every launch into a custom sysadmin project.
The live story
handout.iamthat is the first SLD.
The first subdomain was added through Handout's SLD review and guarded install flow, then checked in SkyInclude Browser.
HTTP and HTTPS both stay enabled.
The first release should not force HTTPS redirects. HTTP keeps current HNS browsers and proxies usable, while HTTPS remains available for DANE/TLSA-capable clients.
What Handout owns
The technical pieces become a repeatable installer.
The revival release is centered on Knot authoritative DNS, nginx, DNSSEC signing, self-signed TLS certificates, TLSA records, parent record output for Bob or hsd, backups, rollback notes, and public proof artifacts.
Knot serves the TLD zone and managed SLD records.
Self-signed certificates are paired with TLSA records instead of assuming Web2 CA trust.
Generated config is backed up, reviewable, and designed for uninstall or upgrade.
Bob or hsd publication remains a reviewed human step for now.
Next product question
Most people should not need to run the VPS themselves.
The open-source installer matters, but the community also needs a hosted Handout service: a simple dashboard where a TLD owner can add the Bob records once, create SLDs, publish starter pages, and grow into custom hosting later.
Chooses a TLD and copies reviewed NS, GLUE4, and DS records into Bob.
Runs the DNS, DNSSEC, DANE, web server, backups, and proof checks.
Gets real HNS websites without learning every infrastructure detail first.