Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


What kinds of Abuse reports does a Web host generally get?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

What kinds of Abuse reports does a Web host generally get?

JasonMJasonM Member
edited August 2019 in General

Hi
I was going through few threads here which had mention about Abuse reports, DMCA, Email SPAM, Copyright infringements, etc. But none exactly describe "abuse" as in what sense.

So, I was wondering what kind of "abuse" reports does a web host generally get (leaving aside DMCA, Email SPAM, Copyright, Phishing)

Any link to "kinds of abuse people report" will also do.

Comments

  • imokimok Member
    edited August 2019

    According to what I see here (I'm not a provider), spam and cpu abuse is one of them, and mostly because the server was hacked.

    EDIT2: And when the host is the abuser, they are dog rapists.

  • @imok Not sure he means internal reports and the like, I think he means people complaining to them about abuse on their networks.

  • Anything from email spam to bruteforce and CP

    Thanked by 1JasonM
  • tittyfish and bad mental hygiene

    Thanked by 1ITLabs
  • AuroraZ said: Not sure he means internal reports and the like, I think he means people complaining to them about abuse on their networks.

    I meant what type of complaints people send to a web host under the title "abuse reports" to abuse contact email addresses. I'm aware of few kinds that I read here: UCE spam, IP infringements, etc.

  • Bogus/Fake/Incomplete DCMA takedowns of content

    Thanked by 1JasonM
  • Hentai (loli porns. smh...)
    Copy Righted Materials

    Thanked by 1JasonM
  • I would also imagine they would get reports on unlicensed/nulled software the client is running.

    Thanked by 1JasonM
  • FHRFHR Member, Host Rep

    Spam, spam, spam, DMCA, spam, spam, Sony PSN hacking attempts, spam, spam, spam

  • HostSlickHostSlick Member, Patron Provider
    edited August 2019

    Spam, Bruteforce, DMCA, Spamhaus, Phishing, German Authorities, SpamCop,
    And phone calls from German Authorities, K11
    asking if we received their letter, German BKA, Lawyers, Netcraft and so on.

    Anything can happen. I can't list everything, list would go too long

    Thanked by 1JasonM
  • BitNinja reports - your interwebz has started WW3, kindly sign up to us thanking you.

  • @FHR said:
    Spam, spam, spam, DMCA, spam, spam, Sony PSN hacking attempts, spam, spam, spam

    "spam" as in customers asking silly questions listed in the KB or can be searched on Google?

  • @Zerpy said:

    @FHR said:
    Spam, spam, spam, DMCA, spam, spam, Sony PSN hacking attempts, spam, spam, spam

    "spam" as in customers asking silly questions listed in the KB or can be searched on Google?

    Mass email sending.

    Thanked by 1JasonM
  • Running free hosting service, despite crap ton of manual verification, one or two will skip the line.

    Here is by the order:

    Phishing
    Spamming
    Child porn (mostly hentai/Loli crap)
    Failed DMCA

    Thanked by 1JasonM
  • angeliusangelius Member
    edited August 2019

    How do you prevent spamers ?
    You have to let them in, burn an IP, ask the support to change their IP then ban them?
    No way to block/discourage them?

  • @angelius said:
    How do you prevent spamers ?
    You have to let them in, burn an IP, ask the support to change their IP then ban them?
    No way to block/discourage them?

    Setup outgoing limits
    Monitor usage
    Trust Maxmind/FraudLab etc.
    If you want to be tough,
    Ask for ID verification, super strict TOS with collectable fees.

    Thanked by 1angelius
  • Just out of curiosity, if a company hosts a client and they have illegal content (spam/disgusting stuff), and they suspend/terminate them immediately upon finding out, is the host responsible legally?

  • FHRFHR Member, Host Rep
    edited August 2019

    seriesn said: Setup outgoing limits
    Monitor usage

    Doesn't work with unmanaged servers unless you're DPIing customer traffic.

    seriesn said: Trust Maxmind/FraudLab etc.
    If you want to be tough,
    Ask for ID verification, super strict TOS with collectable fees.

    Does literally nothing against spam.

    seriesn said: Trust Maxmind/FraudLab etc.

    Customers with black hat demands generally know their way around these systems.

  • @FHR said:

    seriesn said: Setup outgoing limits
    Monitor usage

    Doesn't work with unmanaged servers unless you're DPIing customer traffic.

    Works pretty decent on shared hosting. Specially when you have user with crapton of emails going out and bouncing back.

    seriesn said: Trust Maxmind/FraudLab etc.
    If you want to be tough,
    Ask for ID verification, super strict TOS with collectable fees.

    Does literally nothing against spam.

    Fends off the basic ones. Something is better than nothing.

    seriesn said: Trust Maxmind/FraudLab etc.

    Customers with black hat demands generally know their way around these systems.

    Totally.

    These are all that just prevents a little. Nothing is perfect :)

    Thanked by 1FHR
  • jackbjackb Member, Host Rep
    edited August 2019

    @FHR said:

    seriesn said: Setup outgoing limits
    Monitor usage

    Doesn't work with unmanaged servers unless you're DPIing customer traffic.

    You don't need inspect packet contents (DPI) in order to detect most forms of DoS, attempted amplification attacks, bruteforce attacks; detect and/or rate limit spam at a virtualization host or network level. Packet headers are sufficient.

    Copyright infringement via torrents is the one that easily slips by.

  • FHRFHR Member, Host Rep
    edited August 2019

    jackb said: You don't need inspect packet contents (DPI) in order to detect most forms of DoS, attempted amplification attacks, bruteforce attacks or spam at a virtualization host or network level. Packet headers are sufficient.

    Sorry, I should've clarified, I was talking specifically about spam detection. As far as I'm aware, one of the only ways is looking into packet contents on port 25/tcp and looking for "MAIL FROM" or similar

  • jackbjackb Member, Host Rep
    edited August 2019

    @FHR said:

    jackb said: You don't need inspect packet contents (DPI) in order to detect most forms of DoS, attempted amplification attacks, bruteforce attacks or spam at a virtualization host or network level. Packet headers are sufficient.

    Sorry, I should've clarified, I was talking specifically about spam detection. As far as I'm aware, one of the only ways is looking into packet contents on port 25/tcp and looking for "MAIL FROM" or similar

    A hashtable of 25/tcp and source ip is fine for rate limiting, no need to inspect contents. I would even suggest that it is best not inspecting contents even if beneficial for spam filtering purposes, as unless your customers opted in to outbound filtering, the contents of the packet may be off limits even for automatic analysis in certain jurisdictions (e.g. Likely the EU)

Sign In or Register to comment.