Beware of Namecheap.com big problems

[nsacm]

I registered a .cm domain through them. Zero problems for months. Didn't change a thing ever. about 14 days ago my domain name just stopped working.

They have provided me with little to no info on the matter. They have deleted my comments on their facebook fan page and kicked me off the fan page.

I spent quite a bit of money branding this site and it is in ruin now because of them.

They have blamed enom and the .cm registery. I have seen no reports anywhere else beyond them on this issue.

If you value your business, stay away from namecheap.

 

[lothos]

welcome to namepros.

Can you send a private message to me with the domain name?

 

[nsacm]

nsa.cm

---------- Post added at 03:29 PM ---------- Previous post was at 01:39 PM ----------

sorry for posting the link

 

[wot]

I registered a .cm domain through them. Zero problems for months. Didn't change a thing ever. about 14 days ago my domain name just stopped working.

They have provided me with little to no info on the matter. They have deleted my comments on their facebook fan page and kicked me off the fan page.

I spent quite a bit of money branding this site and it is in ruin now because of them.

They have blamed enom and the .cm registery. I have seen no reports anywhere else beyond them on this issue.

If you value your business, stay away from namecheap.

Never had a problem with them, one of my favorite registrars and support is normally spot on. Perhaps you should refer back to them without the public name calling?

 

[focuspro]

It's one of my favorite registrars so far.
recently, it has DNS problems.(fixed)
__________________
Focus on Your Site

 

[malcarada]

I took all of my domains out of NameCheap after two years ago they charged me $30 because Google Checkout rejected my valid credit card.

They went on and on about their credit rating and how I should pay a penalty because my valid credit card was refused by Google Checkout. They also locked me out of my account and domains until I paid.

Cutting the story short, I opened a thread at a well known webmasters forum where someone from NameCheap helped me out with the case and then refunded my money based on a technicality. (The transaction was accepted then refused in under 5 seconds).

But NameCheap would deffend its right to charge people a "penalty" if the credit card is has reversed charges (by them) and I was pointed out to their terms and conditions.

Totall BS I have to tell you, if a credit card is not valid that is fair, but if a cc is valid and a company rejects it, then that is your problem.

Maybe NameCheap can clarify if they still have a policy where they charge people a penalty when their VALID credit card is charged then has charges reversed by them.

 

[lothos]

nsa.cm

I'm showing that domain is still registered, have you tried the namecheap live support? Or using different nameservers?

 

[Dave_Z]

I can't post a link to another forum, but the same issue has been discussed in WHT. Assuming what's
posted there is true, apparently the .cm Registry "disabled" certain domain names for whatever "odd"
reason.

From what's described, it seems the OP's domain name was inadvertently one of them. Unfortunately
not much can be done except to wait for NameCheap or whoever to press them to fix it.

 

[lothos]

after reading around for a while, the problem appears to be with the .cm TLD and not with namecheap. It sounds like namecheap has gone out of their way to help.

Blame lies with .CM, not with Namecheap IMHO.

 

[Domagon]

This again illustrates the risks of using county-code TLDs instead of an ICANN regulated gTLD.

The ccTLD country (Cameroon for .CM) can change the rules any time! The registrant, most often, has no effective recourse other than, maybe, getting a refund / credit for something else.

On a related note, ccTLD registry agreements often mention in the fine-print that the controlling ccTLD country ultimately has authority.

And the issue of retroactively changing policies is not limited to lesser known ccTLDs ... even .US has retroactively taken domains back ... ie. F*uckCensorship.US - it registered, resolved, etc and then was taken back ... do a whois on it ... stuck in perpetual limbo - yep, ironic, .US censors!

In short, the problem you experienced is a blessing in disguise - branding a ccTLD is often a bad idea - find and brand a nice domain in a gTLD (.com, .net, .info, etc), and use the ccTLD (nsa.cm) domain as a redirect and/or sub-section of the gTLD branded site.

Ron

 

[labrocca]

Certainly not something Namecheap or Enom had any control over. OP you need to adjust your blame meter a bit.

 

[Kate]

Cameroon has a reputation for being very corrupt, no idea about the registry but it was clearly a high-risk extension.

TBH I find it hard to understand why would someone want to actually develop a business around and brand a .cm domain. IMO doing so would drive traffic to nsa.com because many people would think it's a typo of .com :p

Some ccTLDs are mature and run in a professional manner but in the more backwater ones anything goes.

 

[snicksnack]

Our customers can update their .CM domains without any problems and I spoke with some people how have their domains at Moniker and they also do not have the problem.

 

[snicksnack]

it seems your site is working again. I guess your posting has helped.