Banning domains

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • thonglife
    So Fucking Banned
    • Oct 2004
    • 1566

    #1

    Banning domains

    Any suggestions on whether or not to ban - country/top-level? My htaccess has a few dozen IP's of bandwidth hogs (and of course the reg .mil/.gov) but I wanted to see if anyone out there bans entire countries? ie.. .mx, .cn, etc.. Gigs of traffic going to third-world countries and shit for sales, so I'm not sure...
  • SinSational
    Confirmed User
    • Oct 2004
    • 1723

    #2
    i've never done that. do you have some type of password sharing script in place? is the bandwidth legit or are people sharing passwords?

    ICQ# 273099174 - monthly specials - 2 Month Free Credit on All Plans - 100% Referrals - chris@ for details
    Virtual from $14.95/month, Dedicated from $149.95/month
    Dual-Core Xeon > 1000GB @ $149.95 | 1500GB @ $169.95 | 10Mbps @ $269.95

    Comment

    • thonglife
      So Fucking Banned
      • Oct 2004
      • 1566

      #3
      I host a free affiliate site and run TGPs. I just 403'd an IP in Kuwait who had logged 1655 minutes of connection time with 71 page views. I've got scripting to stop all the fusker-type hotlinking, however, I'm at odds on how to deal with visitors from the Phillipines, Mexico, China and Korea using site-rippers. They rank among the highest bandwidth users and I'm not getting any referral sales. Not sure if folks are just using open-proxies or what - but I'm getting ready to just ban the top-levels. These countries are burning at least 3 gig a day from me - but I hate to see a legit customer get 403'd.

      Wanted to see what others are doing to deal with this.

      Comment

      • thonglife
        So Fucking Banned
        • Oct 2004
        • 1566

        #4
        Beginning to think it's just gonna have to be on a case-by-case basis. I've been careful not to ban backbones, thus far. I just wish there was an easier way or if CCBill/Verotel provided IP ranges to afillliates. Hell..CCBill just added the time stamp, so I guess IP's won't happen for another year or so.

        BTW: I have yet to find a way to ban WebStripper. - even using the RewriteCond/HTTP_USER_AGENT} command. It does nothing and I've already had a rather "nice" discussion with the guy who wrote the code for this "browser" - mind you a browser that ignores robots.txt and doesn't identify itself in log entires.

        Comment

        Working...