Acceptable Use Policy (AUP)

Acceptable Use Policy

This Acceptable Use Policy ("AUP") applies to all UnderHost services, including shared hosting, offshore hosting, VPS, cloud servers, dedicated servers, reseller hosting, domain services, SSL, CDN, email, support, server management, and related infrastructure.

UnderHost supports privacy-friendly and offshore hosting, but our services may not be used for abuse, fraud, security attacks, spam, malware, CSAM, stolen data, or activity that places our customers, providers, networks, payment partners, registrars, or infrastructure at unacceptable risk.

Reports should be submitted through our CustomerPanel with clear technical evidence.

1. Abuse Review Framework

UnderHost reviews abuse in four practical categories:

2. Prohibited Abuse and Harmful Activity

• Spam and email abuse: unsolicited bulk email, snowshoe sending, forged headers, list bombing, purchased or scraped lists, open relays, compromised mailboxes, excessive bounces, and activity that damages IP or mail reputation.
• Phishing and fraud: credential theft, fake login pages, fake payment pages, brand impersonation, fraudulent shops, financial scams, account takeover, social engineering, and deceptive services.
• Malware and botnets: ransomware, loaders, droppers, exploit kits, command-and-control, botnet activity, malicious redirects, drive-by downloads, backdoors, unauthorized crypto mining, and distribution of harmful code.
• Network attacks: DDoS attacks, brute-force attacks, credential stuffing, unauthorized vulnerability scanning, mass port scanning, packet floods, reflection or amplification traffic, IP spoofing, intrusion attempts, and route abuse.
• Child safety: CSAM, child exploitation, grooming, sexualization of minors, or links, redirects, advertisements, storage, indexes, or facilitation connected to abuse of minors.
• Violence and serious harm: credible threats, terrorist or violent extremist activity, targeted harassment, doxxing, or activity that creates a serious risk to people or the public.
• Illegal commerce: stolen data, payment card data, access credentials, botnet access, malware sales, trafficking, counterfeit documents, unlawful financial services, or other goods or services illegal in the relevant jurisdiction.
• Resource abuse: excessive CPU, RAM, disk I/O, inode, database, email, process, storage, or network usage that degrades service quality, harms other customers, or violates plan limits.

3. Rights, Media and Jurisdiction-Sensitive Complaints

UnderHost is an international and offshore hosting provider. Copyright, trademark, IPTV, streaming, media indexing, linking, adult, speech-related, gambling, regulated product, or content-licensing complaints are not automatically treated as takedown matters merely because a complaint is submitted.

We review these matters according to the selected service location, applicable law, rights documentation, court orders, registrar or registry rules, datacenter and upstream-provider requirements, payment-provider risk, technical evidence, and the customer's response.

• Customers remain responsible for having the rights, licenses, permissions, exemptions, or jurisdictional basis required for their content, media service, product, or platform.
• Complainants should provide specific URLs, timestamps, screenshots, rights ownership details, authorization status, court orders if any, and a clear explanation of the alleged violation.
• UnderHost may reject unsupported private disputes, request additional evidence, ask the customer for documentation, request targeted removal, require relocation or technical controls, disable access to specific material, or suspend unresolved repeat cases.
• Impersonation, counterfeit activity, clear rights abuse, court-ordered restrictions, provider-confirmed violations, or repeated unresolved complaints may result in stronger action.

4. Abuse Reports and Customer Response

Abuse reports must be specific, truthful, and supported by evidence. A useful report includes the affected IP address, domain, URL, email headers, timestamp with timezone, nature of the abuse, screenshots, logs, hashes, file paths, packet captures, or other relevant evidence.

UnderHost may close, reject, or deprioritize reports that are vague, automated without evidence, duplicative, misleading, forged, retaliatory, or submitted to pressure a customer in a private dispute.

Customers must respond promptly and professionally to abuse notices. Unless UnderHost gives a shorter emergency deadline, customers must begin investigation immediately and provide meaningful remediation within the time stated in the notice. Failure to respond, denial without evidence, incomplete remediation, repeated abuse, or allowing the same issue to recur may result in suspension or termination.

5. Fair Resource Usage Policy

6. Shared and Reseller Hosting Abuse

Shared and reseller hosting are shared environments. One account must not consume resources, generate complaints, or create security issues that materially affect other customers or the server.

• Shared hosting may not be used as bulk storage, backup storage, public mirrors, file dumps, software distribution, high-volume media hosting, traffic relay, or intensive compute unless the plan expressly allows it.
• Accounts may be limited for excessive CPU, RAM, disk I/O, IOPS, inodes, processes, database queries, simultaneous connections, email volume, file count, or automated application activity.
• Resellers are responsible for abuse, compromise, spam, fraud, resource usage, support, and policy compliance by their own customers and sub-accounts.
• UnderHost may suspend a domain, email account, database, script, sub-account, reseller account, or entire reseller service where required to protect the platform.
• Customers may be required to optimize applications, add caching, repair databases, remove malware, reduce mailing, clean files, upgrade plans, or migrate to VPS/dedicated service.

7. VPS, Cloud and Dedicated Server Abuse

VPS, cloud, and dedicated services provide greater control, but they also create greater responsibility. Unless a service is expressly managed, customers are responsible for securing and administering the server environment.

• Customers must maintain the operating system, firewall, authentication, services, mail configuration, applications, patches, backups, logs, monitoring, and licenses inside the server.
• Compromised servers that send spam, host malware, attack third parties, run botnet traffic, scan networks, or create complaints may be isolated, filtered, suspended, null-routed, or required to be reinstalled.
• UnderHost may restrict outbound traffic, block ports, require password rotation, require customer remediation, or request evidence that compromise has been cleaned before reconnecting service.
• Customer-caused compromise, misconfiguration, abusive traffic, failed updates, firewall errors, kernel changes, or third-party software failures are not SLA events.
• Dedicated server hardware replacement, KVM/IPMI access, rescue mode, remote hands, reinstallations, and data recovery attempts may depend on location, payment status, abuse status, provider access, and support scope.

8. Network Attacks, Scanning and DDoS

UnderHost does not allow customers to use its infrastructure to attack, probe, disrupt, overload, or unlawfully access third-party systems.

• Prohibited activity includes DDoS attacks, amplification traffic, reflection attacks, packet floods, spoofing, route abuse, unauthorized vulnerability scanning, mass port scanning, brute-force attacks, credential stuffing, and intrusion attempts.
• Security research, penetration testing, vulnerability scanning, or load testing may require prior written authorization and must be limited to systems the customer is authorized to test.
• Services receiving attacks may be filtered, rate-limited, relocated, isolated, or null-routed where needed to protect infrastructure and other customers.
• DDoS protection is mitigation. UnderHost does not guarantee that every attack will be blocked, that latency will remain unchanged, or that service will remain available during all attacks.
• Customers operating high-risk services may be required to use specialized DDoS protection, a suitable location, dedicated resources, or additional filtering.

9. Malware, Botnets and Compromised Content

Malware and botnet activity are severe abuse categories. UnderHost may act immediately when hosted content, server traffic, or account behavior indicates active compromise or harmful code.

• Prohibited activity includes malware hosting, ransomware, exploit kits, droppers, loaders, phishing kits, credential stealers, keyloggers, malicious scripts, drive-by downloads, malicious redirects, and command-and-control infrastructure.
• Customers must remove infected files, patch vulnerable software, rotate credentials, remove backdoors, review logs, and prevent reinfection.
• UnderHost may disable specific files, directories, scripts, domains, mailboxes, databases, or services where targeted action is practical.
• Repeat compromise may require migration, upgrade, application rebuild, managed service, or termination if the customer cannot maintain a clean environment.
• UnderHost may preserve evidence such as hashes, file paths, timestamps, IPs, URLs, and logs for security, abuse, legal, or provider purposes.

10. Phishing, Fraud and Impersonation

Phishing, credential theft, payment fraud, and deceptive services are not protected by offshore hosting and may result in immediate action.

• Prohibited activity includes fake login pages, fake payment pages, credential harvesting, brand impersonation, fraudulent shops, investment scams, tech-support scams, account takeover, and deceptive redirects.
• UnderHost may consider page content, hosted files, form destinations, DNS, redirects, payment flow, domain age, brand references, technical indicators, and complaint evidence.
• Services may be suspended immediately while a phishing or fraud complaint is reviewed, especially where credentials, payments, or public harm are at risk.
• Customers must not move phishing or fraud content between accounts, domains, IPs, or locations to evade enforcement.
• Fraudulent orders, stolen-card use, fake identity information, and chargeback abuse may result in account-wide termination and no refund.

11. Domain, DNS and Registrar Abuse

Domain and DNS services are subject to registrar, registry, ICANN, ccTLD, DNS provider, and legal requirements. UnderHost may be required to act even where hosting content is located elsewhere.

• Prohibited domain abuse includes phishing domains, malware domains, botnet domains, fast-flux abuse, fraudulent WHOIS/RDAP data, domain impersonation, DNS abuse, nameserver abuse, and repeated unresolved rights or fraud complaints.
• Customers must maintain accurate registrant and contact data and respond to registrar or registry verification requests.
• Domains may be suspended, locked, placed on hold, disabled, or referred to a registrar or registry where required by applicable rules or credible abuse evidence.
• Expired, suspended, or legally disputed domains may not be recoverable, and UnderHost does not control all registrar or registry decisions.
• DNS records may be disabled or modified where they point to severe abuse, malware, phishing, active attacks, or provider-confirmed violations.

12. IP Allocation, rDNS and Reputation Abuse

IP addresses are limited network resources assigned for technical need and active service use. They are not sold to customers and remain subject to UnderHost and provider control.

• Additional IPs may require technical justification and may be denied, reduced, reclaimed, renumbered, or replaced for operational, registry, payment, abuse, scarcity, provider, or reputation reasons.
• Customers are responsible for activity that damages IP, ASN, mail, domain, or network reputation.
• UnderHost may suspend outbound traffic, remove rDNS, rotate IPs, refuse replacement IPs, require cleanup, or terminate service after spam, malware, phishing, scanning, attacks, blacklist events, or repeated complaints.
• Reverse DNS may be refused or removed where it is false, misleading, generic in a harmful way, inconsistent with the service, or associated with abuse.
• IP geolocation, blacklist status, search-engine treatment, streaming treatment, third-party classification, and routing reputation are not guaranteed.

13. CDN, Proxy, Cache and Traffic Relay Abuse

CDN, cache, proxy, acceleration, and traffic relay features must be used to support legitimate customer services, not to hide abuse or evade enforcement.

• Customers may not use CDN or cache services to conceal phishing, malware, fraud, attacks, stolen data, CSAM, or other severe abuse.
• UnderHost may purge cache, disable acceleration, reveal origin indicators to appropriate providers or authorities where permitted, require origin remediation, or suspend related services.
• High-volume cache abuse, hotlinking abuse, abusive file distribution, origin overload, or traffic patterns that harm network quality may require a different plan or suspension.
• CDN and proxy services may be subject to third-party provider rules, regional restrictions, sanctions, content rules, and abuse handling requirements.

14. Adult, Gambling and Regulated Content

Some content categories are lawful in one jurisdiction and restricted in another. UnderHost may allow jurisdiction-appropriate content while still requiring lawful operation, proper location selection, and abuse controls.

• Adult content must not involve minors, exploitation, coercion, non-consensual material, trafficking, hidden-camera content, revenge content, or any content illegal in the relevant jurisdiction.
• Gambling, betting, financial services, pharmaceuticals, regulated products, and age-restricted services may require licenses, age controls, geofencing, payment compliance, or a suitable service location.
• Customers are responsible for knowing the laws that apply to their content, target audience, payment flow, business model, and chosen hosting location.
• UnderHost may request documentation, require relocation, impose technical controls, or refuse services that create unacceptable legal, payment, datacenter, registry, or network risk.

15. False, Abusive or Incomplete Reports

UnderHost welcomes legitimate abuse reports, but the reporting process must not be used as a weapon in business disputes, censorship attempts, harassment, or competitive pressure.

• Reports should include evidence and identify the specific content, domain, IP, URL, timestamp, header, or technical indicator at issue.
• False, forged, automated, retaliatory, misleading, or mass-submitted reports may be ignored, deprioritized, blocked, or escalated if they create operational burden.
• UnderHost may require complainants to clarify authority, rights ownership, affected jurisdiction, and technical evidence before taking action.
• Repeated misuse of the abuse process may result in limitations on future submissions or referral to appropriate parties.

16. Repeat Offenders, Linked Accounts and Evasion

UnderHost may consider the broader account pattern when reviewing abuse, not only the single service named in a complaint.

• UnderHost may consider related accounts, shared payment methods, contact details, domains, nameservers, IP ranges, fingerprints, order patterns, tickets, chargebacks, and prior abuse history.
• Opening new accounts, moving services, changing domains, rotating IPs, or using different payment methods to evade enforcement is a material violation.
• Repeated compromise, repeated rights complaints, repeated spam, repeated phishing reports, repeated malware reports, or repeated non-response may result in account-wide termination.
• UnderHost may refuse future orders from customers or patterns associated with prior severe abuse, fraud, chargebacks, or evasion.

17. Anti-Spam and Email Policy

• Email must be permission-based and comply with applicable anti-spam, privacy, consumer protection, and electronic communications laws.
• Purchased, harvested, rented, scraped, or third-party lists may not be used without a lawful basis and appropriate consent.
• Customers must use accurate sender identity, valid reply addresses, working unsubscribe handling, bounce processing, suppression lists, and appropriate SPF, DKIM, and DMARC where applicable.
• UnderHost may impose hourly or daily limits, outbound filtering, SMTP relay requirements, port restrictions, queue removal, password resets, or mail suspension for complaints, spamtrap hits, bounces, compromised mailboxes, phishing reports, or blacklist events.

18. Security and Network Integrity

• Customers must secure accounts, servers, CMS installations, plugins, themes, scripts, databases, mailboxes, SSH keys, private keys, and control panel access.
• Compromised sites, outdated software, weak passwords, exposed admin panels, open relays, and vulnerable plugins are the customer's responsibility even if abuse was not intentional.
• UnderHost may isolate, filter, suspend, null-route, require cleanup, require password rotation, or require reinstall/remediation for compromised services.
• DDoS protection is mitigation, not a guarantee that all attacks will be blocked or that services will remain available during all attacks.

19. Backups and Data Responsibility

• Customers are responsible for maintaining current, independent, and restorable backups of websites, databases, email, files, configurations, licenses, and customer content.
• UnderHost backup services, where offered, are a convenience and may be limited by plan, account size, storage use, abuse status, suspension, technical failure, or backup cycles.
• Accounts over 10GB may be excluded from free shared-hosting backups unless a paid backup service is active or UnderHost states otherwise.
• UnderHost is not liable for data loss caused by customer error, compromise, malware, failed updates, third-party software, external attacks, backup failure, suspension, termination, or events outside UnderHost's reasonable control.

20. Enforcement, Suspension and Termination

UnderHost may warn, request remediation, throttle, filter, block ports, remove content, disable scripts, suspend services, null-route IPs, restrict access, preserve evidence, request documentation, require relocation, terminate services, or report activity where reasonably necessary.

UnderHost may cooperate with datacenters, upstream providers, registrars, registries, certificate authorities, payment processors, anti-abuse organizations, affected parties, and lawful authorities when necessary to investigate, mitigate, report, or respond to abuse, fraud, security incidents, or legal obligations.

Services suspended or terminated for abuse, fraud, severe security risk, non-payment, chargeback, or material policy violation are not eligible for refund or SLA credit.

21. Policy Changes

UnderHost may update this AUP to reflect changes in law, abuse trends, provider requirements, security practices, network operations, or business needs. Continued use of the Services after an update becomes effective constitutes acceptance of the updated AUP.