- Impact
- 87
Hi Name Pros,
I've been using NameSilo for a majority of my domain registrations but recently I noticed a HUGE inconvenience they have caused for me and several investors when simply doing a Google search for the brand that I am developing...
The name of my upcoming brand uses a .COM domain and we are based in the United Stated with upcoming expansions in Mexico, Canada, and several other countries in South America. Our expansions were to be kept confidential until date-of-launch but thanks to NameSilo that was impossible ...
Once confirming our expansions; we wanted to obtain all possibilities (and typo's) of our brand name in ccTLD's and additional .COM's so we purchased the ccTLD's for the brand (E.g., *.mx, *.ca, etc) from other registrars since NameSilo currently does not offer such extensions but also purchased .COM's such as TheBrandsNameMexico.com, TheBrandsNameMX.com from NameSilo ...
One week after purchasing those additional .COM's from NameSilo we noticed them listed on Google (several times, and from different aggregated resources / URL's) when simply Googling the brands name ...
Pretty much all .COM's registered from NameSilo such as TheBrandsNameMexico.com have somehow appeared in Google Search results when simply searching for the brand. Let me be clear, literally ALL domains including the main/root .COM domain we will be using for the brand are 100% untouched. We simply just registered them and left them as-is until it is time for launch.
#1 - All of my NameSilo purchases have their Privacy enabled prior checkout
#2 - Our competition now knows that we are expanding into Mexico, Canada, and the South American countries because of this (... and my investors were PISSED)
How can a completely untouched domain registration be scraped so easily? Do all newly registered domains simply go into some sort of public database? If not, is NameSilo somehow selling my info?
Whatever the case is; they must fix this. Who knows what other information is floating around the web when it SHOULD NOT be (...especially if privacy is enabled and/or paid for)
I've been using NameSilo for a majority of my domain registrations but recently I noticed a HUGE inconvenience they have caused for me and several investors when simply doing a Google search for the brand that I am developing...
The name of my upcoming brand uses a .COM domain and we are based in the United Stated with upcoming expansions in Mexico, Canada, and several other countries in South America. Our expansions were to be kept confidential until date-of-launch but thanks to NameSilo that was impossible ...
Once confirming our expansions; we wanted to obtain all possibilities (and typo's) of our brand name in ccTLD's and additional .COM's so we purchased the ccTLD's for the brand (E.g., *.mx, *.ca, etc) from other registrars since NameSilo currently does not offer such extensions but also purchased .COM's such as TheBrandsNameMexico.com, TheBrandsNameMX.com from NameSilo ...
One week after purchasing those additional .COM's from NameSilo we noticed them listed on Google (several times, and from different aggregated resources / URL's) when simply Googling the brands name ...
Pretty much all .COM's registered from NameSilo such as TheBrandsNameMexico.com have somehow appeared in Google Search results when simply searching for the brand. Let me be clear, literally ALL domains including the main/root .COM domain we will be using for the brand are 100% untouched. We simply just registered them and left them as-is until it is time for launch.
#1 - All of my NameSilo purchases have their Privacy enabled prior checkout
#2 - Our competition now knows that we are expanding into Mexico, Canada, and the South American countries because of this (... and my investors were PISSED)
How can a completely untouched domain registration be scraped so easily? Do all newly registered domains simply go into some sort of public database? If not, is NameSilo somehow selling my info?
Whatever the case is; they must fix this. Who knows what other information is floating around the web when it SHOULD NOT be (...especially if privacy is enabled and/or paid for)