In this exercise we are going to compare .app registrations against .com. The same exercise can be applied to other nTLDs. Materials needed: .com zone file .app zone file I used today's zone files. The counts are as follows: .com: 133051790 unique domains .app: 198097 unique domains The goal is simple. For every .app domain registered and found in the .app zone file, let's find out if the .com 'counterpart' is registered. For the purpose of this analysis the counterpart means this: domain + 'app' + .com For example if abc.app is registered, we check if abcapp.com is registered. We could also check if abc.com is registered, as there must be a few domains registered in .app that are available in .com (and other extensions) I will spare you with the scripting here, and cut to the chase. Out of 198097 .app domains, 45876 'counterparts' are found in the .com zone file. That is 23.16%. The difference is 76.84%. So that means that three quarters of all registered .app domains are not registered in their .com 'equivalents', if only for defensive registration purposes. In my humble opinion, it is not a good idea to register a nTLD while leaving the .com counterpart unregistered. Why: bleeding traffic, defensive registration etc. Also, buying something.app when somethingapp.com is not even registered suggests that it is a dubious investment in the first place, because the demand for the combo does not even exist in .com. Again, just imho. Besides, the vast majority of registered domain in .app probably don't make sense, and are not really usable for any practical purpose.