- Impact
- 3,974
This is all just my opinion. Wondering if I was the only one who felt this way...
The more ridiculous the extension the more I'm starting to feel as some of these extensions are simply coming out for the purpose of extorting defensive registrations from those who have brands that already end with the word in the TLD. There is no real demand or practical use for certain TLDs except to create a hack and a hack on brands that are already trademarked and/or already being used.
Letting just anything, just any word become a gTLD and not requesting feedback from the public like they do with zoning laws on brick and mortar stores was highly irresponsible and I'm predicting we're going to see a TON of backlash in the years to come once businesses and trademark holders really catch on and trademark holders get tired of this whole defensive-reg/udrp charade. We're already seeing problems slowly unfold now with the Bloomberg situation, how much has gTLDs cost them so far between UDRPS, disruptions to their business and defensive registrations? What does this mean to the smaller business that can't afford to play this game?
Some extensions are worthwhile, they have a purpose, an underlying value to those who register them because they represent categories (app, tv, photos, etc) Then there's some that have no true value or purpose except to make a mockery out of the entire gTLD concept and put out a HACK on popular brands and trademarks.
When a new gTLD is created don't you think it's taken into consideration how many .COMs, etc are registered that end with that word? Example .dog, I just seen this one is coming out, seriously.... What is the purpose to put this on the internet? Except that there are already tens of thousands of .COM domains (or brands) that end with 'Dog". Thousands of established businesses and trademarks, HungryDog, GameDog, WorkingDog, etc. Now it's either PAY UP to acquire your Hungry.DOG, Game.Dog, etc or risk someone else operating on a confusing version of the name you been using for years and possibly disrupt your business. And the same applies to the next one, and the next one, and the next one?
For example, I acquired a great KeywordHoldings.com domain, I had to pay and will have to continue to pay mid $xx on a defensive reg .holdings and I didn't want to, I have no interest in it, I don't want a .holdings domain but I feel forced, I can imagine how other brand owners feel when the renewal is $xxx - $xxxx, and to say this isn't a part of the strategy today with many of these new gTLDs coming out would be ignorant. When you see some of these ridiculous extensions coming out that have no practical use or represent something meaningful, think about the hacks they make and how many trademarks brands are already operating on the phrase because I believe the owners of that gTLD thought about it already.
I think that's why it's more important than ever to secure and operate your .COMs, at the end of the day the traffic to your website will never leak to your hack counterpart, but that is something the hack will always have to worry about.
The more ridiculous the extension the more I'm starting to feel as some of these extensions are simply coming out for the purpose of extorting defensive registrations from those who have brands that already end with the word in the TLD. There is no real demand or practical use for certain TLDs except to create a hack and a hack on brands that are already trademarked and/or already being used.
Letting just anything, just any word become a gTLD and not requesting feedback from the public like they do with zoning laws on brick and mortar stores was highly irresponsible and I'm predicting we're going to see a TON of backlash in the years to come once businesses and trademark holders really catch on and trademark holders get tired of this whole defensive-reg/udrp charade. We're already seeing problems slowly unfold now with the Bloomberg situation, how much has gTLDs cost them so far between UDRPS, disruptions to their business and defensive registrations? What does this mean to the smaller business that can't afford to play this game?
Some extensions are worthwhile, they have a purpose, an underlying value to those who register them because they represent categories (app, tv, photos, etc) Then there's some that have no true value or purpose except to make a mockery out of the entire gTLD concept and put out a HACK on popular brands and trademarks.
When a new gTLD is created don't you think it's taken into consideration how many .COMs, etc are registered that end with that word? Example .dog, I just seen this one is coming out, seriously.... What is the purpose to put this on the internet? Except that there are already tens of thousands of .COM domains (or brands) that end with 'Dog". Thousands of established businesses and trademarks, HungryDog, GameDog, WorkingDog, etc. Now it's either PAY UP to acquire your Hungry.DOG, Game.Dog, etc or risk someone else operating on a confusing version of the name you been using for years and possibly disrupt your business. And the same applies to the next one, and the next one, and the next one?
For example, I acquired a great KeywordHoldings.com domain, I had to pay and will have to continue to pay mid $xx on a defensive reg .holdings and I didn't want to, I have no interest in it, I don't want a .holdings domain but I feel forced, I can imagine how other brand owners feel when the renewal is $xxx - $xxxx, and to say this isn't a part of the strategy today with many of these new gTLDs coming out would be ignorant. When you see some of these ridiculous extensions coming out that have no practical use or represent something meaningful, think about the hacks they make and how many trademarks brands are already operating on the phrase because I believe the owners of that gTLD thought about it already.
I think that's why it's more important than ever to secure and operate your .COMs, at the end of the day the traffic to your website will never leak to your hack counterpart, but that is something the hack will always have to worry about.
Last edited:














