That was a fascinating write-up! I too immediately looked for `domain.name` registration and would have marked it up to DNS trickery after that gave a NXDOMAIN. I'm glad you followed the rabbit down the hole on this one. I've added the resolving domains to my Pi-hole block list: https://www.github.developerdan.com/hosts/
Thanks!:) What was even more confusing, but I didn't mention in the article, was that visiting domain.name in my browser did take me to a similar website. That was because firefox will try www.<doman.tld> when <domain.tld> fails, so it was actually www.domain.name I was getting instead of domain.name. This behavior can be turned off by setting `browser.fixup.alternate.enabled` to false.
I had no idea about that config, but I've seen the behavior before. That behavior is even more interesting considering that Firefox will hide the 'www' subdomain in the URL[1]. So not only will it silently add the www, but it also won't show it in the URL! SMH!
