Quick answer: Cloud2Y prohibits using services for spam, network scanning, DDoS participation, malware or phishing hosting, unlicensed content distribution and other illegal activity. Abuse reports are investigated; depending on severity you get a deadline to fix the issue or the service is suspended immediately. Compromised servers count too — secure yours.
Overview
Abuse rules protect the network's reputation — IP ranges used for spam or attacks get blacklisted, which hurts every customer. The policy applies whether abuse is intentional or the result of your server being hacked; the difference shows in how the case is handled, not in whether it is handled.
Before you start
Prohibited on all Cloud2Y services (non-exhaustive; see the AUP overview):
- Sending unsolicited bulk mail or operating open relays.
- Port scanning, brute-forcing or attacking third parties; participating in DDoS (including "stressers").
- Hosting malware, phishing pages, botnet C2 or stolen credentials.
- Copyright-infringing distribution and any activity illegal in the service's jurisdiction.
- Interfering with the network or other customers (allowed and prohibited network use).
Step-by-step guide
How abuse handling works and how to stay clear of it:
- Reports arrive (spamtraps, complaint feeds, third parties) and are verified by the team.
- You are notified via ticket/email with the evidence and a required action — respond there, even if you disagree.
- Severe or ongoing abuse (active attacks, phishing) can mean immediate suspension to protect others; lesser cases get a fix-by deadline.
- Repeated or unremedied abuse leads to termination under the service terms.
- Prevention: run the security checklist, keep software updated, and tell support proactively if your server was compromised — cooperation is credited.
Common issues
- "It wasn't me, I was hacked": plausible and common — but you still must contain and fix it; see the incident guide.
- Ignoring abuse tickets: silence reads as unwillingness and accelerates suspension.
- Grey-area projects: mass mailing, scraping, proxies — ask support first whether your use case is acceptable.
When to contact support
Open a ticket to respond to an abuse notice, to report abuse you observe from other hosts, or to clarify whether a planned workload complies with the abuse handling policy before you build it.
Frequently asked questions
What activities are prohibited on Cloud2Y servers?
Spam, port scanning and attacks on third parties, DDoS participation, hosting malware or phishing, distributing infringing content, and anything illegal in the service jurisdiction.
What happens when an abuse report arrives about my server?
The report is verified and you are notified via ticket with the evidence and a required action. Severe active abuse can mean immediate suspension; lesser cases get a fix-by deadline.
My server was hacked and sent abuse — am I liable?
You are expected to contain and fix it: the policy applies regardless of intent. Respond on the ticket, follow the incident guide, and proactive cooperation is taken into account.
Related articles
- Acceptable Use Policy overview
- Abuse handling policy
- Allowed and prohibited network use
- What to do if your server is hacked
Need a hand? Contact Cloud2Y support →
