1. 24

  2. 9

    I’ve independently reproduced the results for .com and .blog, and identify CentralNic, a TLD infrastructure service provider, as the common backend for some of the slowest TLDs.

    1. 3

      I think the top comment from HN is well worth to be quoted here:

      I know this is actually quite interesting, but before you start worrying about the latency of the name servers of your TLD, you might want to do something about the metric ton of JavaScript on your site and the 25 different 3rd party servers from which you side load most of it. Also those 6 additional servers from which you load a bunch of TTF fonts. Especially if all your site does is just display some text and two or three pictures.

      Source: https://news.ycombinator.com/item?id=22010593

      1. 2

        Interestingly, the .io, so loved by tech, is 5x slower than the top records.

        1. 1

          Another concern I have with these TLDs is that many of them are run by private companies. What if they decide that they no longer want to host .ninja because it’s not a good ROI? Or what if the company goes belly-up?

          1. 2

            Almost every single TLD is run by a private company. This problem isn’t unique to the newer TLDs.

            1. 1

              They will probably sell off their existing customer base (i.e. the domain name holders) to another company with better operating margins.

              1. 2


                Personally, I’d rather not stake my business’ stability on that.

                1. 1

                  That’s a valid concern, I was for some reason thinking about personal domains only.