Acceptable Use Policy

Defined abuse of services:

• Unsolicited communications
  • Communications sent without consent (implied or otherwise) via email or any other communication medium.
• Malicious use
  • Any site, page, or download intended to defraud users by impersonating another service in order to gain unauthorized access to accounts or information (phishing).
  • Any type of software, script, code, or file intended to harm systems or users, or to improperly benefit from them, including Malware, RATs, Ransomware, Port Scanning or DDoS tools.
• Illegal use
  • Hosting content that is illegal in the country where the service is operated.
• Resource abuse
  • Intentionally or unintentionally consuming more than your fair share of resources on the node where the service resides.

Action

• Intentional abuse
  • Intentional abuse is grounds for immediate service suspension or termination.
  • No refunds or compensation will be provided.
  • Data may be disclosed to law enforcement if required by a valid court order or warrant.
  • The user will be permanently prohibited from holding services with Ko-Net. Any attempt to evade this restriction, even with non-abusive services, will result in termination.
• Unintentional abuse
  • Unintentional resource abuse typically results in rate limits being applied. Except for bandwidth, no rate limits are enforced by default.
  • Depending on severity, the service operator may be contacted and given 24–72 hours to resolve the issue.
  • In rare cases, services may be immediately null-routed, such as during detected botnet activity.
  • Failure to resolve unintentional abuse may result in service suspension.

We generally give benefit of the doubt towards deeming intentional and unintentional abuse and we aim to cooperate with our customers to resolve any cases of abuse.

Please note that we are currently not permitting any exit nodes, this is temporary until we have our own IP space, below is the future TOR policy and will apply when customers are moved onto our IP space. Relays are still permitted.

Our policy on TOR nodes is as follows:

Rules for both Relays and Exits:

• Contact us before any setup, we may suspend any tor nodes that are set up without making us aware.
• Configure torrc to stay within your traffic allowance.
• Let us know your domain so we can set Reverse DNS for the IP, we follow the set standard of tor-exit.yourdomain.tld
• Keep your software up to date.
• Ensure you have a functional landing page for your hostname and reverse dns which explains you are a tor node.
• Setup a local DNS cache with Bind9 or Unbound to handle DNS efficiently.

Rules for Exits:
We require you to implement an exit policy which blocks at minimum all of the following:

• 22 (SSH)
• 25 (SMTP)
• 465 (SMTP over SSL)
• 587 (SMTP over TLS/Submission)

We recommend you also block:

• Ports 6660-6667 (IRC - Kerbs DDoS)
• 6697 (IRC over SSL - Kerbs DDoS)
• We may request you block further ports if we are experiencing a high number of abuse complaints from them.

We welcome TOR nodes on our services, thank you for contributing to the TOR network!

Please also consider running a Bridge or Snowflake instance instead, these help too.

Please note that although we permit exit nodes and are more lenient towards reports involving services hosting one, we do still check abuse reports for them, so please do not attempt to hide behind hosting one if you are otherwise acting maliciously.

We reserve the right to refuse consent for any TOR node, we typically would only exercise this in the unlikely case of a shortage of network resources on the node or our network that can be allocated towards it.