zlacker

[parent] [thread] 9 comments
1. highcl+(OP)[view] [source] 2022-08-15 15:02:56
Note on recommendations of namecheap in this thread. My experience with namecheap is very bad too. They also send emails like godaddy saying if you don't respond in a short time(24 hours) your domain will be revoked. Related experience: https://news.ycombinator.com/item?id=14139288 I moved my domains from namecheap to gandi.net and so far no problems. I would avoid namecheap like the plague for any large site.

ycombinator uses gandi.net too.

[Edit] Added 24 hours to short time

replies(4): >>Charle+R1 >>skykoo+X2 >>dolive+K9 >>boole1+4a
2. Charle+R1[view] [source] 2022-08-15 15:10:17
>>highcl+(OP)
To save you a click, “short time” for NameCheap = 24 hours, not 2.
replies(1): >>highcl+vd
3. skykoo+X2[view] [source] 2022-08-15 15:14:49
>>highcl+(OP)
I've also had a similar issue where gmail filed namecheap's domain notification emails into "spam" leading to a domain expiring; I don't know whether that's really an issue with namecheap or with gmail's spam filter, though.
4. dolive+K9[view] [source] 2022-08-15 15:47:36
>>highcl+(OP)
It feels like we can find experiences like this one on any registrar.
replies(1): >>katbyt+qe
5. boole1+4a[view] [source] 2022-08-15 15:48:48
>>highcl+(OP)
We also had a problem with namecheap threatening to turn off one of our production domains unless we immediately removed a page hosted at a particular URL. Apparently they had received a complaint from a third-party anti-phishing company [1] which said we were hosting a phishing page at that URL. It was a complete false alarm as we were definitely not hosting a phishing page! This would have been obvious to any human actually looking at the page. However, when we tried to argue this with namecheap support, they informed us that the only way not to have our domain promptly shut down was to either remove the page OR get the third-party company to confirm to namecheap that our page was not a phishing page (!). In other words, they would not even look at the page themselves and use their common sense to confirm it wasn't a phishing page. We briefly tried to contact the third-party company, but we were not able to get any sort of response from them at all. So we just took our page down. Namecheap support then confirmed that we would not be losing our domain this time, but shockingly followed up that if they received a single further complaint that our entire account would be shut down permanently as they have a single-strike rule. We promptly migrated our ~50 domains to another registrar.

[1] These companies are hired by organizations like banks to scour the web for phishing sites and have them shut down by reporting them to their hosting providers and/or domain registrars. Obviously our legitimate page was incorrectly flagged by whatever algorithm the company used.

replies(1): >>dahdum+nl
◧◩
6. highcl+vd[view] [source] [discussion] 2022-08-15 16:02:55
>>Charle+R1
Didn't realize that might be annoying... I added 24 hours to the comment.
replies(1): >>Charle+Xz
◧◩
7. katbyt+qe[view] [source] [discussion] 2022-08-15 16:08:27
>>dolive+K9
Any company really.
◧◩
8. dahdum+nl[view] [source] [discussion] 2022-08-15 16:37:41
>>boole1+4a
Do you run any type of ad network on your site? The hijacking can be rather targeted (geo, device, time of day, etc..) such that you could never recreate on your own.

I still see this occasionally on otherwise innocuous sites.

Other 3rd party JS can still cause it, but ad networks are the most common.

replies(1): >>boole1+cU
◧◩◪
9. Charle+Xz[view] [source] [discussion] 2022-08-15 17:39:59
>>highcl+vd
Not annoying, just thought it was interesting to surface since otherwise readers might’ve assumed they gave you 2 hours notice. (Thanks!)
◧◩◪
10. boole1+cU[view] [source] [discussion] 2022-08-15 19:21:12
>>dahdum+nl
No, there were no ads anywhere on the domain in question.

There was text on the page that matched the name of a large financial institution. My suspicion is that this caused the problem.

[go to top]