Page 1 of 2 12 LastLast
Results 1 to 25 of 40
  1. #1

    A few questions for Richard (enetwork) from Namecheap

    Hi Richard

    Let me open this by saying I am not Namecheap-bashing in any way, shape or form. These is are genuine questions.

    A few times I've had attempts to post comment spam on my gallery, with the spamvertised domain having been registered by Namecheap, and the spammer hiding behind your Whoisguard service. When your firstliners on the support desk have been informed by the proper channels, the response has been either that:
    1. Namecheap are not hosting the domain, or
    2. Namecheap will not divulge the real contact details.


    Now in cases of 1, I'm well aware of that, and the hosting provider has been contacted too, and in case of 2, I've never once requested that Namecheap does divulge the real contact details to me.

    However, the reports I submit clearly state that the reason why the report was submitted to your support desk is because the spammer is using your Whoisguard service in violation of the Whoisguard ToS. However much I try to get this through to the support desk staff, the mantra of 1 & 2 above is repeated ad nauseum.

    In light of the fact that I've had no success in finding a direct email address for you (Which, again, is understandable - there are many crazies out there), I've come here to ask, as you seem to be fairly active and responsive here.

    so....

    Question 1: As the registrar of the spamvertised domains, and provider of the Whoisguard service that the spammers are using to hide behind, is there any policy within the company to deal with spammers using the Whoisguard service, if clear proof is provided that the spammers are doing so?
    Question 2: If the answer to the above is yes, where should I report this abuse of your services to? I have not had much luck so far via the support@namecheap.com address

    If you require, I can provide you with the latest ticket number via PM

  2. #2
    Join Date
    Sep 2008
    Location
    Sydney Australia
    Posts
    580

  3. #3
    Join Date
    Feb 2011
    Posts
    71
    To be honest, I would really start to think twice whether to keep my domain name with any registrar who would give every single detail about me to a random Joe who walks in with a few pieces of paper claiming I am DDOSing/attacking his website...
    I definitely have no sympathy towards spammers and I think all those people should be punished. However, from Name Cheap's perspective, I think it is reasonable for them to make sure that the spamming is indeed the case (i.e., investigate the evidence you have provided), and see if your claim is true. And even if in the case your claim is true, the suspension/legal action should be taken by Name Cheap and not you, right?
    Just my $0.02.

  4. #4
    Quote Originally Posted by geekinfinance View Post
    To be honest, I would really start to think twice whether to keep my domain name with any registrar who would give every single detail about me to a random Joe who walks in with a few pieces of paper claiming I am DDOSing/attacking his website...
    Did you not understand this:

    Quote Originally Posted by FredFrog
    I've never once requested that Namecheap does divulge the real contact details to me.
    Quote Originally Posted by geekinfinance View Post
    I definitely have no sympathy towards spammers and I think all those people should be punished. However, from Name Cheap's perspective, I think it is reasonable for them to make sure that the spamming is indeed the case (i.e., investigate the evidence you have provided), and see if your claim is true. And even if in the case your claim is true, the suspension/legal action should be taken by Name Cheap and not you, right?
    Just my $0.02.
    or this:

    Quote Originally Posted by FredFrog
    Question 1: As the registrar of the spamvertised domains, and provider of the Whoisguard service that the spammers are using to hide behind, is there any policy within the company to deal with spammers using the Whoisguard service, if clear proof is provided that the spammers are doing so?
    I have no interest in pursuing spammers through legal channels. I also have no interest in the "real" details that the spammers would have registered with Whoisguard - they're spammers, remember, do you think they'd actually have real details registered? What I would like to see, though, is entities enforcing their ToS, and sending a clear message to these scumbags that their custom is not welcome.
    Last edited by FredFrog; 02-25-2011 at 09:08 PM.

  5. #5
    Quote Originally Posted by EmuHost-Pete View Post
    Try here

    <URL deleted due to constraints>
    Thanks - unfortunately, that would not work, it's for email spam, not comment spam. I would also require an email address for the automated spam traps, online submissions are no good.

  6. #6
    Join Date
    Nov 2009
    Location
    Neenah, WI
    Posts
    388
    Quote Originally Posted by FredFrog View Post
    A few times I've had attempts to post comment spam on my gallery, with the spamvertised domain having been registered by Namecheap, and the spammer hiding behind your Whoisguard service
    1. Comment spamming while annoying is NOT illegal in the United States.

    2. How can you possibly even have any idea that it was the person that owns the domain that left the comments?

    If it was so easy to cause trouble, then people would just comment spam their competitors out of business.

    Just delete the comments if they bother you. You just wasting NameCheap's time, they are never going to do anything about it. Because; see commend 1 & 2 above.

  7. #7
    Join Date
    Oct 2010
    Posts
    1,784
    Why not report the offending IP to the spammers hosting provider instead of going through the registrar, and simply block the IP?

  8. #8
    Join Date
    Nov 2009
    Location
    Neenah, WI
    Posts
    388
    Quote Originally Posted by geekinfinance View Post
    claiming I am DDOSing/attacking his website...

    Wait, who said anything about a DDOS? I thought we were talking about comment spam, which is NOT a criminal act. A DOS attack is illegal. However with a DDOS in inherently virtually impossible to prove who initiated the attack.

  9. #9
    Quote Originally Posted by jamiedolan View Post
    1. Comment spamming while annoying is NOT illegal in the United States.
    Which is, of course, not the point. The point is that the spammer is using Namecheaps service in contravention of Namecheaps ToS. What's the point of have ToS if you're not going to bother enforcing them?

  10. #10
    Quote Originally Posted by TheJoker View Post
    Why not report the offending IP to the spammers hosting provider instead of going through the registrar, and simply block the IP?
    Comment spam very rarely originates from the host of the site being spamvertised. And the spamtrap automations DO report to the spammers hosting provider, and the owner of the IP range containing the originating IP address.

    However, making life as difficult as possible for spammers is a good thing. Which is why any spammer misusuing WHOIS masking services, against the ToS of that WHOIS masking service, are also reported to the owners of the service, so that they may enforce their ToS by slinging the scumbag OFF their service.

  11. #11
    Join Date
    Nov 2009
    Location
    Neenah, WI
    Posts
    388
    Quote Originally Posted by FredFrog View Post
    Which is, of course, not the point. The point is that the spammer is using Namecheaps service in contravention of Namecheaps ToS. What's the point of have ToS if you're not going to bother enforcing them?
    Again; How can you prove that it is the owner of the domain that is doing the spamming?

  12. #12
    Join Date
    Feb 2011
    Posts
    71
    My bad, for some reason I missed that line...
    However, in that case what do you expect to hear from NameCheap? "We have canceled the domain and fined the spammer x dollars"?
    I highly doubt that will be the answer they'll give.
    Quote Originally Posted by FredFrog View Post
    Did you not understand this:





    or this:



    I have no interest in pursuing spammers through legal channels. I also have no interest in the "real" details that the spammers would have registered with Whoisguard - they're spammers, remember, do you think they'd actually have real details registered? What I would like to see, though, is entities enforcing their ToS, and sending a clear message to these scumbags that their custom is not welcome.

  13. #13
    Join Date
    Feb 2011
    Posts
    71
    Again, my bad, I was just giving an example and used DDOS to refer to any action that would potentially screw websites...

    Quote Originally Posted by jamiedolan View Post
    Wait, who said anything about a DDOS? I thought we were talking about comment spam, which is NOT a criminal act. A DOS attack is illegal. However with a DDOS in inherently virtually impossible to prove who initiated the attack.

  14. #14
    Join Date
    Jan 2011
    Location
    Ohio
    Posts
    467
    I'm sure they have logs showing what IP requested to use their service, and what domain they went to. If you have logs/comments showing the date, and time then they should be able to just check the logs and see what IP it is, and then you could block that IP from your site all together. I guess thats the problem here though.. They wont tell you the ip right? I say just put something important on there, get like 10 people to buy it, and then file a lawsuit against them for not following their TOS, and file for loss of income..

  15. #15
    Join Date
    Nov 2009
    Location
    Neenah, WI
    Posts
    388
    Quote Originally Posted by bluemer View Post
    I'm sure they have logs showing what IP requested to use their service, and what domain they went to. If you have logs/comments showing the date, and time then they should be able to just check the logs and see what IP it is, and then you could block that IP from your site all together. I guess thats the problem here though.. They wont tell you the ip right? I say just put something important on there, get like 10 people to buy it, and then file a lawsuit against them for not following their TOS, and file for loss of income..
    Ever here of an anonymous proxy? The people leaving those comments are using proxies, and it is highly unlikely that the proxies are keeping logs. If they do, your going to have one heck of a time getting a hold of them. Then on top of that, your going to have an even harder time proving it was the domain owner. Most of the time third parties are going to be hired to leave these comments.

    I'm not sure exactly what your talking about, but you can't sue someone for not abiding by another companies TOS.

    You're not going to get a domain disabled for comment spam and your not going to win a law suite.

    There is nothing you can do but delete the comment.

  16. #16
    Quote Originally Posted by geekinfinance View Post
    To be honest, I would really start to think twice whether to keep my domain name with any registrar who would give every single detail about me to a random Joe who walks in with a few pieces of paper claiming I am DDOSing/attacking his website...
    I definitely have no sympathy towards spammers and I think all those people should be punished. However, from Name Cheap's perspective, I think it is reasonable for them to make sure that the spamming is indeed the case (i.e., investigate the evidence you have provided), and see if your claim is true. And even if in the case your claim is true, the suspension/legal action should be taken by Name Cheap and not you, right?
    Just my $0.02.
    I think you may like to choose internetbs because they totally have whois privacy and its free with every domain.

    and they have 24/7 live chat support and i think they are also non-us.

  17. #17
    Quote Originally Posted by FredFrog View Post
    Which is, of course, not the point. The point is that the spammer is using Namecheaps service in contravention of Namecheaps ToS. What's the point of have ToS if you're not going to bother enforcing them?
    One catch to that is who exactly is going to determine if NameCheap's TOS is being violated.

    Think of it like I put a do-not-step-on-my-grass sign on my lawn. One day a good friend comes over, but inadvertently steps on my grass as I come out to welcome him.

    You tell my good friend, "Hey, don't step on that guy's lawn!", I wave you thanks, and both my friend and I walk in while stepping over my grass. Well, who decides that?

    Anyway, just PM user enetwork or mdrussell with specifics about this. Or can't you put in some script or so to screen out comment spam like WordPress does?

  18. #18
    Quote Originally Posted by jamiedolan View Post
    Again; How can you prove that it is the owner of the domain that is doing the spamming?
    Contrary to popular belief, it is rarely worth the time, effort and money for an individual to spamvertise a rivals site. Every attempt to do so can also inadvertently raise the profile of the rivals site, thus rendering the exercise counter productive.

  19. #19
    Quote Originally Posted by geekinfinance View Post
    My bad, for some reason I missed that line...
    However, in that case what do you expect to hear from NameCheap? "We have canceled the domain and fined the spammer x dollars"?
    I highly doubt that will be the answer they'll give.
    I would expect them to want to enforce their ToS

  20. #20
    Quote Originally Posted by jamiedolan View Post
    Ever here of an anonymous proxy? The people leaving those comments are using proxies, and it is highly unlikely that the proxies are keeping logs. If they do, your going to have one heck of a time getting a hold of them. Then on top of that, your going to have an even harder time proving it was the domain owner. Most of the time third parties are going to be hired to leave these comments.
    Which is indeed what happens. However, most free proxies are not anonymous. Reports to paid proxies see the spammers lose their proxy account, something which they factor into their costs.

    Quote Originally Posted by jamiedolan
    You're not going to get a domain disabled for comment spam and your not going to win a law suite.
    Do you really think so? I've caused hundreds of spamvertised domains to be disabled over the years. Without ever having to file a lawsuit (Which would be a waste of time anyway)


    Quote Originally Posted by jamiedolan
    There is nothing you can do but delete the comment.
    I don't even need to do that - the comments never make it on to the gallery, the automations which make the notifications see to that.

  21. #21
    Quote Originally Posted by Dave Zan View Post
    One catch to that is who exactly is going to determine if NameCheap's TOS is being violated.

    Think of it like I put a do-not-step-on-my-grass sign on my lawn. One day a good friend comes over, but inadvertently steps on my grass as I come out to welcome him.

    You tell my good friend, "Hey, don't step on that guy's lawn!", I wave you thanks, and both my friend and I walk in while stepping over my grass. Well, who decides that?

    The analogy falls down in several areas. Here are just two:

    • The spammers are not Namecheap's friends. They are paying for a service provided by Namecheap, which is supplied to them on condition they do not break the rules.
    • Allowing your friends to wallk on your grass is not going to harm your reputation. Allowing spammers to use a service provided, however, will. One would think that Namecheap would be interested in protecting their reputation.



    Quote Originally Posted by Dave Zan
    Or can't you put in some script or so to screen out comment spam like WordPress does?
    You must have missed this bit:

    Quote Originally Posted by FredFrog
    And the spamtrap automations DO report to the spammers hosting provider, and the owner of the IP range containing the originating IP address.
    The specific code I wrote for Coppermine has been downloaded thousands of times, and is used a large number of Coppermine galleries. The authours of automated backlinkers have even had a go at trying to circumvent it, with no success. There is constant moaning on the bhseos forum (home of Backlinker) about it. Suffice to say, the comments never make it on to the galleries either.

  22. #22
    Quote Originally Posted by FredFrog View Post
    The analogy falls down in several areas. Here are just two:

    • The spammers are not Namecheap's friends. They are paying for a service provided by Namecheap, which is supplied to them on condition they do not break the rules.
    • Allowing your friends to wallk on your grass is not going to harm your reputation. Allowing spammers to use a service provided, however, will. One would think that Namecheap would be interested in protecting their reputation.
    Heh, analogies are never perfect, but as long as they help understand or make a point. Point here is that only NameCheap will decide if their TOS is being violated or not, despite what others tell them.

    I guess blocking the domain in question from your gallery won't work either? Or just PM the two users I mentioned previously and see how it goes.

  23. #23
    Quote Originally Posted by Dave Zan View Post
    Heh, analogies are never perfect, but as long as they help understand or make a point. Point here is that only NameCheap will decide if their TOS is being violated or not, despite what others tell them.

    I guess blocking the domain in question from your gallery won't work either? Or just PM the two users I mentioned previously and see how it goes.
    How exactly does one block a domain? You can block incoming traffic from an IP address, but not a domain. Considering that domains are portable with respect to IP addresses, and that incoming traffic comes from an IP address, not a domain, what you're saying really makes little sense. There are methods of blocking via content of the posted comment (Akismet, for example), but this is still not "blocking a domain".

    Invariably, the spam originates from an IP address that is not the IP address of the host the spamvertised site is hosted on. Spammers are stupid, but not many are THAT stupid.

    Back to the real point - Yes, it is up to Namecheap to decide if their ToS has been violated. But if they're not informed about the activity their "customers" undertake while making use of (And violating the conditions of) their service, how are they to even know that they have the decision to make? And who gets to make that decision? A firstliner who can't even understand what's being reported to them? Unfortunately, while everyone knows what email spam is, not many know what comment spam is. This is true of support staff too.

  24. #24
    Quote Originally Posted by FredFrog View Post
    How exactly does one block a domain?
    I just figured there's maybe a script, Apache command or whatever that blocks off or filters anything with a specific word or so. Depends how your gallery is created.

    If NameCheap's higher-ups taught their first or second-line people to handle certain issues in certain ways, then I guess that's how they want to do it. You can push it as far as you can, and their manager or so can also finally say, "Sorry, but our decision" despite the possible repercussions.

    Just do what you can.

  25. #25
    Join Date
    Jan 2011
    Location
    Ohio
    Posts
    467
    You can block a domain.. I did a google search, and http://httpd.apache.org/docs/2.2/howto/access.html

    "If you wish to restrict access to portions of your site based on the host address of your visitors, this is most easily done using mod_authz_host."

    "The Allow and Deny directives let you allow and deny access based on the host name, or host address, of the machine requesting a document. The Order directive goes hand-in-hand with these two, and tells Apache in which order to apply the filters.
    "

    So I would think if you really wanted you could simply block the hostname used by the namecheap proxy.. or block multiple of their proxies..

Page 1 of 2 12 LastLast

Similar Threads

  1. HELP! Namecheap.com's enetwork
    By bluechinagroupltd in forum Domain Names
    Replies: 5
    Last Post: 05-17-2008, 10:29 AM
  2. eNetwork - NameCheap - please read
    By Minn Soe in forum Domain Names
    Replies: 1
    Last Post: 08-09-2007, 06:07 PM
  3. eNetWork@Namecheap.com, SOS
    By mydomainissue in forum Domain Names
    Replies: 1
    Last Post: 08-09-2007, 05:58 PM
  4. enetwork from Namecheap
    By mv808 in forum Domain Names
    Replies: 8
    Last Post: 09-14-2006, 11:24 AM
  5. Namecheap (enetwork) please help me
    By ekind in forum Domain Names
    Replies: 33
    Last Post: 06-24-2006, 02:24 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •