There is no business model behind has-a.name. It's main motivation came from our customers, who are using the IPv6VPN quite intensive. Many of our customers ar

There is no business model behind has-a.name. It's main motivation came from our customers, who are using the IPv6VPN quite intensive. Many of our customers are app developers (ruby, python, clojure, you name it) and they develop on their notebooks that are IPv6 enabled (usually a /64 or /48 per device). To be able to share in-development state with other remote developers, the common thing to do would be to pass around a http://[2a0a:e5c0:...] http://[2a0a:e5c0:...] url that was http only. This is not only cumbersome (no one likes to type square brackets), but also potentially risky, as there is no MITM protection whatsoever. To fix this problem we created has-a.name, because customers/developers now go ahead and just create a docker container and share it as https://2a0a-e5c0-...has-a.name https://2a0a-e5c0-...has-a.name with their co-developers. Because our whole company consists of a bunch of Open Source Hackers we decided to make it public to allow others work around the same problem. Even though we promise to never change the automatic resolution (that's work, doesn't make sense to do that for us), you don't have to trust has-a.name. You can register your own domain and replicate our setup and use your domain instead. I hope that clarifies a bit the business model question.