Log in

No account? Create an account

Previous Entry | Next Entry

Namecheap: Why I'm moving away from them

I have a rather extensive collection of Web sites, where I write about everything from photography to transhumanism to sex. As a result, I have rather a lot of domain names, which until recently I've registered with Namecheap, as they have in the past been cheap and reasonably reliable.

However, I have begun the painful and expensive process of moving off Namecheap, and I recommend others do the same. There are two interrelated reasons for this, the first having to do with poor support and training (Namecheap employees don't appear to know the differnce between a domain and a subdomain, which is rather a serious problem when you're in the business of domains) and the second having to do with support for spam and malware (largely on account of the first).

The story is long and complicated, but it begins many months ago with a spam email advertising life insurance, which was plugging a domain hosted on Namecheap Hosting.

Namecheap, in addition to being a domain registrar (well, technically a reseller for a registrar called Enom), is also a Web hosting company. If you're a Web hosting company, sooner or later a spammer will host a Web site with you. How you react when you receive abuse reports will determine how popular you are with spammers. If you react quickly, spammers will avoid you. If you allow the site to remain up, spammers will talk, and soon other spammers will flock to you. If you continue to leave spam domains up, pretty soon spammers will start choking out your other customers.

Anyway, it happens. A spammer found Namecheap Hosting. I hadn't seen much spam on Namecheap before, so I fired off an abuse report and that was the end of it.

Or so I thought. But then things took a turn for the strange.

A couple of days later, I received an email from Namecheap abuse saying "we aren't hosting this domain, go complain to someone else." Now, that happens from time to time as well; spammers will sometimes hop from one host to the next, so by the time a host receives a complaint, the spammer's Web site has been moved and they're not hosting it any more.

I looked at the domain. Still hosted on Namecheap. I wrote back saying "no, it's definitely hosted by you guys; here's the IP address, That address is in your space."

And got back a second email: "We're not hosting this site."

"Huh," I thought, "that's strange. Maybe the site is hosted on many IP addresses?" That's another spam tactic, putting a Web site on a bunch of hosts and then changing the IP address constantly. But no, the site had only ever been hosted by Namecheap.

I replied and said "no, here's the DNS entry, ere's the history for the site, you're definitely hosting it." And got back yet another reply: "no we're not."

And then something even weirder happened.

I started getting tons of spam advertising domains pointing to Namecheap's IP address space. Tons. Spam advertising life insurance, promoting Bitcoin schemes, advertising phony "cures" for diabetes. Spam pitching window replacement services, Amazon gift cards, Russian dating sites, and home refinancing.

And I'd seen this spam before. It was word-for-word and image-for-image identical to spam from well-known, infamous spam purveyors that had always, until now, advertised sites hosted in Russia, Columbia, and the Ukraine--places that tend to permit spam hosting.

I started getting multiple pieces of this spam a day. Then dozens. All of it advertising domains on Namecheap IP addresses.

Left: Old spam advertising a site hosted in Eastern Europe. Right: Recent spam advertising a site on Namecheap.

I sent spam reports to Namecheap...and Namecheap's abuse team kept sending responses saying "we aren't hosting these sites."

This is the point where I learned that Namecheap, a company that sells domain names, does not understand how a domain name works.

A typical domain name has three (or more) parts. The parts are separated by periods. Let's look at an example:


Going from right to left: The last part is called a "top level domain," or "TLD". It's things like ".com" or ".net" or a country-specific code like ".ca" (for Canadian sites). The UK uses ".co.uk" for various historical reasons.

The part before the TLD, in this case morethantwo, is the domain name.

The part at the very beginning, in this case www, is a subdomain. The subdomain "www" stands for "World Wide Web" and it's the most common subdomain by far. But you can make a subdomain be anything you want. You could set up your Web site at "polyamory.morethantwo.com" or "groupsexisawesome.morethantwo.com" or anything else you like.

And here's the important part:

You can put a subdomain on a completely different server, hosted by a completely different Web host.

For example, morethantwo.com is hosted by Incubus Web hosting. But if I wanted to, I could put "polyamory.morethantwo.com" on Dreamhost and "groupsexisawesome.morethantwo.com" on Softlayer--each subdomain can get its own IP address and its own Web server, if you want.

Now you might not know that, and you can be excused for not knowing that. It's not necessary to understand how the Internet works in order to use it.

But Namecheap should know that. They sell domain names. This is what they do.

It's okay if a person who owns a car doesn't know that a car's engine has more than one spark plug in it, but no professional mechanic should ever be ignorant of that simple fact. It's okay if a person who uses the Web, or even a person who owns a Web site, doesn't know that subdomains can be hosted on one IP address. It's unforgivable that a domain registrar doesn't know that.

In this case, the spammer is using domain names that look like


"view1" is a subdomain, hosted by Namecheap. The main domain,gnrlbshomes.us, is hosted elsewhere. Namecheap's abuse team doesn't know how that works. When they received the spam complaint, they didn't look at view1.gnrlbshomes.us, they only looked at gnrlbshomes.us.

When I figured out what was happening, a light dawned. I fired off a reply explaining that view1.gnrlbshomes.us and gnrlbshomes.us were hosted at differnt IP addresses, and they were hosting the actual spamvertised URL, view1.gnrlbshomes.us.

Problem solved, right? They simply missed the subdomain, right? Wrong.

Elena, it seems, didn't talk to Kate. Namecheap has a systemic problem. This isn't someone not noticing the subdomain, this is someone not knowing how domains work.

And I got a lot of these emails, from all different people: "The domain 'blah blah blah' isn't hosted by Namecheap."

At this point, I was convinced the problem was incompetence...and a bizarre incompetence, an incompetence on the level of a professional auto mechanic not understanding that an engine has more than one spark plug.

But then, things took a turn for the even weirder.

I patiently replied to each of the emails, showing the IP address of the main domain and the subdomain, and that the subdomain was in fact on Namecheap IP space.

And then I started getting replies like this:

Essentially, what this says is "if you don't actually send email from a Namecheap server, you're welcome to spam a domain that lives in Namecheap space and we're A-OK with that."

Now, spammers almost never send emails from the same servers their Web sites live on. Usually, spammers send emails from home computers that are infected with viruses without their owner's consent (a lot of computer viruses are written for profit; the virus authors infect computers with software that allows them to remotely control the computers, then sell lists of infected computers to spammers, who use the infected computers to send spam email.) Sometimes, the spam emails are sent from "bulletproof" spam mail servers in places like the Ukraine. But they almost never come from the same computer that's hosting a site.

So Web hosting companies want to see a spam with full headers when you report spam, so they can verify that, yep, this is a spam email, and shut down the Web site that's being spamvertised.

But not Namecheap. Namecheap will knowingly and willingly allow you to spam domains on their servers, provided the spam email doesn't actually come from the same server.

I asked if their policy was to permit spam that doesn't originate from the same server as the Web site, I received this reply:

Which to me looks like a "yes."

At the moment, I am currently receiving 11 spam emails a day advertising domains that resolve to Namecheap IP addresses. There are about half a dozen products being spamvertized; each day's crop of spam messages are word for word and image for image identical to the previous day's, but the domains are different. Clearly, the spammers feel they've found a good home in Namecheap.

So I took a look at that IP address, It's quite a mess.

Domains on are all forwarded; that is, is a pass-along to other IP addresses. If you want to put up a Web site and you don't want anyone to know who's really hosting it, you can put it there, and visitors will be invisibly passed along to its real home.

Now, can you guess what sort of thing that's useful for?

If you said "spam and malware!" you're absolutely right. A Virustotal analysis of shows that it's being used to spread a lot of bad stuff:

And it's not just Virustotal. A Google search for shows that it has a reputation as a bad neighborhood in a lot of places. It's listed as a bad actor in the Cyberwarzone list:

and as a virus distributor in the Herdprotect list:

At this point, I got tired of making screenshots, but basically this Namecheap server has a bad reputation everywhere.

So whether through gross incompetence or active malice, Namecheap is running a server that's a haven for spammers and malware distribution.

Which is why I've begun pulling my domain name registrations from them. I can not in good conscience spend money to support a company that's such a menace to the Internet, and I spend about $500 a year in registrations.

Now, interestingly, I'm averaging about 11 spam emails a day advertising domains on Namecheap's IP space, but I'm averaging 20 spam emails a day that are word for word identical to these but aren't advertising a domain on Namecheap.

The ones that are advertising domains not on Namecheap are advertising domains hosted by a company called Rightside.co, a Web host I'm not familiar with.

As I mentioned before. Namecheap is a reseller for a registrar called Enom. And Rightside.co, well...

The fact that the same spammer is using Namecheap and Rightside, and they're both front-ends for Enom, is interesting. Stay tuned!


( 6 comments — Leave a comment )
Apr. 9th, 2015 08:59 pm (UTC)
Seems like the whole webserver is a spammer organization, now. The rise in received spam mails, after you complained is...curious.

Apr. 16th, 2015 12:49 am (UTC)
Had the same experience
I got the same kind of spam, reported it, and got the same responses initially, later just silence. I wrote about it on my blog, here: https://www.feise.com/~jfeise/blogs/index.php/2014/11/16/namecheap-or-when-good-registrars?blog=8

I have since moved all my domains away from Namecheap.
Jul. 16th, 2015 04:46 pm (UTC)
Spam after domain name purchases
I just had a very strange experience after using namecheap for the first time- two days after buying and receiving confirmation for my domain registries, I received another email saying that because I hadn't responded to an earlier verification email, my purchases had been cancelled?!

I tried to log in on their site and did so semi-successfully- it seemed my services were blocked and I need to message such-and-such for further assistance. I did so, quite angrily but with some tact, got an auto reply, and then... Nothing. Except a sudden barrage of spam for hosting, SEO, etc.

I'm so very, very glad I used paypal and not a credit card to make my purchases. I haven't bothered to check the availability of my domains on whois yet, because I'm sure they're being held for ransom. I found so much good press about namecheap, so this is a serious disappointment and major hassle.
Jul. 19th, 2015 10:54 pm (UTC)
Rightside owns Enom, and is really Demand Media
Came across this while considering pulling things from Namecheap. I have different issues with them, don't entirely dislike them, but have serious concerns about them having their entire support organization in Ukraine. And Billing. And Risk Management. And their convoluted everything-outsourced, much-offshored, company arrangement bothers me. Especially since they are not very transparent about it.

Rightside is the domain registry and registrar part of Demand Media. The (in)famous "content farm". Traditionally the domain business of DM was its only consistently profitable business unit. Rightside is a re-name of that business unit of Demand Media. Allowing both a partial spin-off (I believe it is still partially, maybe still majority- owned by DM) and a public image distance from the somewhat toxic "Demand Media" reputation among some observers. Demand Media does not own Namecheap, neither directly nor indirectly via Rightside owning Enom because Enom does not own Namecheap. But Namecheap absolutely requires Enom, a subsidary of Rightside, a partial subsidiary of Demand Media, in order to function as a Domain Name Registrar.

Namecheap is California is pretty much a "virtual company".

As you discovered, and many technical folks know, they use Enom as the real registrar. Even though Namecheap itself is an ICANN-authorized registrar, and several years ago posted on their site and on web hosting and domain related forums that they would be transistioning to do their own registration, as far as I can tell, they have not. All the domain registration official "contact verification" emails required by ICANN, and the actual whois info (done via a proper Unix/Linux command line whois, not on some whois website at NC or elsewhere) clearly show that ENOM is the register of record.

Which has occassionaly led to big disconnects on the rare times I have a domain support issue. Ticket or chat is with "Namecheap Support" (really, company Zone3000 that NC sort-of implies they own) in Ukraine. Who have told me, "We have to check with the registrar." WAIT - aren't YOU the registrar? No, they are not.

Namecheap Hosting is actually relatively good, certainly better than GoDaddy hosting, if you are one of the foolish people who think that Hosting and Domain Registration should be done at the same place (NO! Run. It's a trap!) Which nobody should normally do even at BestRegistrarAndHostInTheWorld or FluffyBunnyWithUnicornKittenHosting. But it is also almost a separate company, with a to-the-public unmentioned, "competing" company called Web Hosting Buzz, whose President and Founder of that competitor just so happens to be the head of hosting at NC too.

NC just seems to be lacking in transparency about how they operate, who owns them, who they own, where they do support, etc. But there exist tales on the internet where, web hosting talk, happens, about how a dispute on one service will tie up another. Maybe less so that at BogBadDaddy hosts-registrars, but still an icky situation. Especially since Namecheap domain registration agreement not only lacks explicit "You own your domain" language like the most ethical registrars such as Gandi have, but also does HAVE specific "No ownership interest" language outright saying you do not own any intellectual property rights in your domain name.

So become more aware of what they do, and who they are. I continue to have some services at NC but I decreasingly use them for things I consider important.
Jan. 29th, 2017 12:25 am (UTC)
ENOM NameCheap spam partnership
I became deluged with ENOM / NameCheap spam beginning on Jun 2016 and I get from 2-4 spam emails from one or the other each day since then and continuing up through today. Unfortunately, my spam filter catches only about 5% from each registrar.

Here is the way my history transitioned. The initial roll out with me as a target started June 2016 and with all of the spam coming from ENOM registered domains. I kept sending abuse@enom daily reports all went ignored. No response whatsoever. So I wrote to the BBB and reported them as being a spam haven partner and after about a week, to my surprise ENOM responded back through the BBB and with that stated they had killed all of the domains I had reported as well as sent me a list of the twelve or so they had deleted. Still this meant little, since the spammer relies on the domain to be productive primarily on the day the spam email is delivered. Well further complaints to ENOM seemed to fall on deaf ears and the spammer moved to using the.co registrar while attempting to depend on the language barrier to stop reports to the .co organization of the bogus WhoIS contact data (I took care care of reporting to them because I am bi-lingual).

Now today the only process that seems to work against ENOM/ NameCheap spam partnership is to report to the registar's regulating authority the bogus name, address and phone for the domains that are being logged into WhoIS. This still takes up to a week to process, so the spammer and their ENOM / NameCheap spam partner still is virtually unaffected.

Today the spammers have shifted back to NameCHeap almost exclusively and the spammer seems to no longer care that invalid whois data reports are being sumitted to ICANN and the Columbian .co authority, since the evil deed they are doing is completed long before any authority can get to the queue to take down the domain.

NameCheap differs primarily from ENOM in that while ENOM pretends to "take spam seriously" they will do nothing regarding your reports for several days, assuming they do anything at all, and then they make a whoopla about taking action long after it is too late to stop the payload of "first responders" to the spam emails. NameCheap differs in that their abuse@namecheap will blatantly tell you they don't get involved in customer's spamming activity and suggest you take it up with some legal authority, saying their hands are tied.

Speaking of legal authority, does anyone know of any lawyer that would take on a class action lawsuit and file it against NameCheap and ENOM? It seems that the loss of more money than their $10 - $40 daily spammer windfall may be the only language that these two can understand.

Aug. 12th, 2019 10:51 am (UTC)
Where are you moving your domains to?
( 6 comments — Leave a comment )