The internet has a basement, and someone just figured out how to hang a poster on its wall. The .arpa top-level domain is supposed to be sacred ground — reserved for critical infrastructure like reverse DNS lookups — but nothing in the specs actually stops you from abusing those records to serve a website. This post walks you through doing exactly that, step by gleeful step. The mechanism is beautifully indirect. You sign up for a free IPv6 tunnel at Hurricane Electric's tunnelbroker.net, which hands you a routed /64 prefix. That prefix, reversed and dotted, becomes your domain under ip6.arpa. You don't need to own the IPv4 address you provide — it just needs to respond to pings. The author casually pinged news.ycombinator.com and used its IP. Hurricane Electric doesn't verify ownership. Once you have the tunnel, you delegate the reverse DNS to deSEC (Cloudflare reportedly chokes on these domains), point a CNAME at Surge's free static hosting, and you're live. The whole chain — tunnel provider, DNS host, web host — is free. The author even hosts a mirror of the blog post itself on their .arpa domain as proof of concept. The HTTPS situation is the one genuinely interesting technical wrinkle. Most certificate authorities refuse to issue certs for .arpa domains, so you're stuck with plaintext HTTP unless you want to fight that battle separately. The author flags this but doesn't solve it, which is honest — it's a real limitation, not a footnote. What makes this work as a piece of writing is its tone. There's no pretense that this is useful. It's a hack in the original sense — finding unintended behavior in a system and exploiting it for the joy of exploitation. The fake registration info, the borrowed IP address, the cheerful acknowledgment that none of this was intended by the RFC authors — it reads like a love letter to the internet's remaining cracks. The post also nods to a predecessor: e164.arpa, an older scheme that mapped phone numbers to DNS records. German and Czech users can still register there. This lineage matters because it shows the pattern isn't new — infrastructure TLDs have always had soft edges where determined tinkerers can set up camp. This is a five-minute read that will teach you something about how DNS actually works, how reverse lookups are structured, and how much of the internet runs on trust rather than enforcement. It won't change your life, but it will make you smile if you're the kind of person who finds joy in things working in ways they weren't supposed to.
