It looks very very vibe coded. Maybe try a different design approach, the idea generally sounds interesting
On the about page: "AI helped create this site, but I'm responsible for the content, so please let me know about any mistakes."
(I know pgl has been collecting DNS weirdnesses for years - that bit definitely hasn't been AI-generated.)
Makes it even more important to put on a more unique design. Not fancy, just not the most default design any coding AI would create. I am sure many people instantly click away when they see that as well.
It's missing perhaps the most classic of all: someone hosted the DeCSS script (for bypassing the DRM in DVDs) in DNS around 2000.
At some point I hosted my blog in DNS; it was a bunch of chunks in TXT records which the frontend would reassemble. It had really strange side effects, e.g. editing a post could shuffle the chunks but then they'd end up being cached separately and some people would see weird artefacts in the text.
The various "VPN/IP over DNS" solutions miss a typical, more performance variant: VPN over UDP/53. Because DNS is frequently not filtered in badly locked down hotspots.
iodine automatically detects this and switches to boring IP encapsulation if this is the case
... and? Not clear what that has to do with the preceding comment.
I don't really understand the point of TLDs like .museum. They always seem a bit naff. Like why would you want to go to dave.accountant or whatever?
Its a fun thing to put on your business card or GitHub profile, for people not early enough to have "lastname.com/net/org" registered.
I've been trying to find a list I had previously of sites hosting webpages at top-level domains. I think there was a webpage you could access at http://ai./ for a long time.
I miss Granite Canyon :(
A shameless plug for my own project where the DNS infrastructure plays a key role. The idea is to make a chain of TXT records where anyone with a domain name can join the chain my adding a TXT record pointing to the parent domain. https://recordrelay.net