Namecheap Blog

DNS is inherently fault tolerant. That's why you can specify more than one NS record (if server A is down, go to server B!) on a domain. Unfortunately if you use Namecheap's DNS service, you CAN'T specify failover / secondary DNS servers. This has been a known issue for a year & a half that they've failed to address: https://community.namecheap.com/forums/viewtopic.php?f=6&t=5905

Namecheap. Seems to be the favorite among the HN crowd. Also, they donate to EFF. Oh, and gandi.net for TLDs I can't get from namecheap, like .io, .cx. http://community.namecheap.com/blog/2011/12/29/25000-eff-donation/

Someone at Namecheap decided to change their functional domain management interface into "better" one - driven by javascript, with humongous fonts, message popups and dynamic forms that makes any domain editing and management job a time wasting disaster. Namecheap called it "more user friendly and has a modern design". I thought 1and1 and Godaddy were unbeatable but never expected my favorite namecheap to beat them to pulp in pissing off so many users in such a short period of time. As a response to their customers namecheap published a thread: https://blog.namecheap.com/we-are-listening/ Where ironically "listening" ears were closed to any new comments due to overwhelming negative feedback. Namecheap stance is instead of giving users the interface and productivity they really liked - they intent to continue forcing users to "like" their new disastrous UI by promising to publish "Get Started wizards" to ease pain: https://community.namecheap.com/forums/viewtopic.php?f=10&t=43083#… I welcome feedback here and let make namecheap listen to us - the customers that loved and recommended namecheap to all our friends and clients. I also welcome to discuss alternatives to show namecheap that ignoring users is not an option and is not acceptable.

After a raft of social engineering attacks on it's SMS-only 2FA system Namecheap promised to introduce Authy-based authentication instead back in May 2017. Instead, they rolled out a custom solution called OneTouch which requires the Namecheap mobile app and is still tied to your phone number...and doesn't actually integrate Authy or TOTP based passwords https://blog.namecheap.com/authy-based-2-factor-authentication-is-comi…

I did not know that! Looks like[1] it went live back in July. I still wish they'd have used TOTP rather than this onetouch thing that's restricted to a single app, but just about anything was better than SMS, so this is a welcome development. [1]: https://blog.namecheap.com/announcing-onetouch-2fa/

https://blog.namecheap.com/we-say-no-to-sopa/ "At Namecheap, we believe having a free and open Internet is the only option that will continue the legacy of innovation and openess that stands for everything we all value in our modern society." --Namecheap CEO Richard Kendall, 2011 I'm curious what changed.

Can we change the link to the actual blog post from Namecheap that contains considerably more content and less advertising? https://blog.namecheap.com/inciting-violence-vs-freedom-speech/

Quote from https://blog.namecheap.com/we-say-no-to-sopa/ "Why are we against the proposed SOPA legislation? It’s very simple; at Namecheap, we believe in internet freedom. When you register a domain name, you can do anything you wish with it within the confines of the law." You find how much you believe in your principles, when they lead to outcomes you don't like. Given their actions now, namecheap's SOPA opposition now sounds like just a cheap publicity trick they did to distinguish themselves from GoDaddy.

As of January, 2014 Namecheap said[1]: "Currently, we only accept SMS authentication but Google Authenticator, Authy, and TOTP authentication are planned." More than three years seems to me a long development cycle to add TOTP support. Am I being disingenuous to think they just don't care? [1] https://blog.namecheap.com/account-security/

Namecheap only supports SMS 2FA. The have been suggesting they will support Authenticator for years now https://blog.namecheap.com/two-factor-authentication/ Pretty unacceptable considering how important domain control is.

Namecheap: https://blog.namecheap.com/cloudflare-security-incident/

Good luck with that, people have been requesting for TOTP support on Namecheap for the past 3 years. https://www.namecheap.com/support/knowledgebase/article.aspx/9253/45/h… https://blog.namecheap.com/two-factor-authentication/ Here's a list of alternatives someone asked a month ago: https://news.ycombinator.com/item?id=13484739

Let's not throw personal attacks at me (and the tongue-in-cheek "congrats for being promoted to executive!" comment). There's plenty of remorse and there's plenty of acknowledgment of mistakes here. That said, as we acknowledged elsewhere, we're responding to the matter across several different platforms and specifically say we're rushed in trying to get out some basic insights behind what happened and transpired. A more well crafted blog response for all to see (this time from the CEO) has been published to https://blog.namecheap.com/social-engineering-issue/

A happy NameCheap user for years, I have started switching away. Their horrid "modern" 40px padding everywhere bubbly redesign makes GoDaddy look good in comparison. A major pain to manage more than a couple of domains, and numerous user feedback seems to fall on deaf ears, e.g. [1][2][3][4] Example weird feature: all domains are shown, even ones that you've let expire/sold years ago, and there is no way to hide them. [1] https://community.namecheap.com/forums/viewtopic.php?f=10&t=7949 [2] https://community.namecheap.com/forums/viewtopic.php?f=10&t=66644 [3] https://community.namecheap.com/forums/viewtopic.php?f=10&t=65871 [4] https://community.namecheap.com/forums/viewtopic.php?f=10&t=43083

Oops, they deleted it. It was a post from Namecheap answering somebody asking if they were going to support Let's Encrypt. Original question: https://twitter.com/matbacon89/status/667348413470650370 Person's response: https://twitter.com/matbacon89/status/667348648741744640 In between, they _did_ say something like "You'll have to wait and see! :)" I wonder if they deleted it in light of this blog post, which I find disingenuous: https://blog.namecheap.com/ssl-from-namecheap-whats-the-difference/

Plus their TTL policies/issues: https://community.namecheap.com/forums/viewtopic.php?f=6&t=8630

Direct link http://community.namecheap.com/blog/2014/09/01/urgent-security-warning…

Permalink results in 404, but the post is still viewable on the blog homepage: http://community.namecheap.com/blog/

Namecheap.com uses 2FA. http://community.namecheap.com/blog/2013/10/08/two-factor-authenticati…

Yep http://community.namecheap.com/blog/2011/12/22/we-say-no-to-sopa/ http://www.namecheap.com/moveyourdomainday.aspx http://community.namecheap.com/blog/2012/01/18/blackout/

Ok. So accepting bitcoin, but they still won't have things like two-factor auth available for "several months" (reference: https://community.namecheap.com/forums/viewtopic.php?f=10&t=4766). I realize PR departments are probably flailing wildly over $33 bitcoins, but which feature do you think your users are more likely to use?

"Perhaps this is in response to Ghandi's similar offer?" It's the other way around: Gandi's offer was posted on Dec 29 [0], while Namecheap's offer was announced on Dec 27 [1]. [0] https://www.gandi.net/news/en/2011-12-29/539-gandi_supports_the_eff/ [1] http://community.namecheap.com/blog/2011/12/27/move-your-domain-day/

I found the community manager response from NameCheap rather interesting. Looks like they did attempt to reach out which is what I would have expected prior to such a blog in the first place. http://community.namecheap.com/blog/2011/12/26/godaddy-transfer-update…

It looks like they did reach out to them, according to this post at least: http://community.namecheap.com/blog/2011/12/26/godaddy-transfer-update…

NameCheap's folks have stated pretty unequivocally that they did contact GoDaddy ahead of time. I tend to believe them over GoDaddy. http://community.namecheap.com/blog/2011/12/26/godaddy-transfer-update…

GoDaddy has responded to the allegations from namecheap at TechChrunch, saying that the blocks were part of standard practice to limit the volume of Whois queries from a single IP, which is apparently common practice, unless the registrar is notified that there may be a large number of queries. [1] If this is indeed true, then it seems namecheap are trying to score cheap PR points, although they have responded saying they attempted to reach out to GoDaddy.[2] I'm inclined to believe that namecheap did try to reach them, although I'm not sure that they are above trying to slam more bad press onto GoDaddy.... [1] http://techcrunch.com/2011/12/26/godaddy-responds-to-namecheap-accusat… [2] http://community.namecheap.com/blog/2011/12/26/godaddy-transfer-update…

A namecheap employee claims that they did contact goDaddy and that they resorted to the PR release only after they couldn't resolve the issue directly with them: http://community.namecheap.com/blog/2011/12/26/godaddy-transfer-update…

This explains it: http://community.namecheap.com/blog/2011/12/26/godaddy-transfer-update…

That hasn't been the case for a few years now. http://community.namecheap.com/forums/viewtopic.php?f=6&t=467

Transfer to: Gandi: https://www.gandi.net/domain/transfer 1and1: http://order.1and1.com/xml/order/DomaininfoMove NameCheap: http://community.namecheap.com/blog/2011/03/30/elephants/ Basically go to any registrars home page and either search for "Transfer" on the page itself or in their search box if provided. They will all offer it together with easy how to steps - and I am sure their support team will help as well. They want your business and will make it as easy as possible.