Hosting Abuse Policy

This Hosting Abuse Policy applies to services provided by Reonr Limited, trading as Reonr. Reonr Limited is based in Port Harcourt, Rivers, Nigeria.

Hosting abuse can harm customers, victims, payment systems, IP reputation, domain reputation, upstream providers, networks, and the public. Reonr may act quickly where abuse creates security, legal, infrastructure, or public harm risk.

This Policy is intended for customers, resellers, abuse reporters, security researchers, affected third parties, and Reonr staff handling abuse reports.

This Policy applies to Web Hosting, cPanel Hosting, WordPress Hosting, VPS Hosting, Dedicated Servers, Cloud Hosting, Reseller Hosting, Plesk and DirectAdmin control panel licenses, DNS Management, Email services, SSL, Backups, Website migration, Support services, and related infrastructure.

It applies to hosted websites, applications, files, databases, mailboxes, DNS records, IP addresses, nameservers, servers, containers, scripts, control panels, reseller sub-accounts, customer users, and traffic using Reonr resources.

Domain-name-specific abuse may also be handled under the Domain Abuse Policy, registrar rules, registry rules, ICANN requirements, NiRA rules, or other domain authority requirements.

Hosting abuse reports should be sent to [email protected]. Reports should be factual, specific, and supported by evidence where possible.

For urgent legal, child safety, active attack, or imminent harm issues, include "URGENT" in the subject line and provide the evidence needed for Reonr to identify the affected resource quickly.

General support requests should be sent to [email protected]. Legal notices and policy questions should be sent to [email protected]. Privacy requests should be sent to [email protected].

A useful report should include the affected domain, URL, IP address, server hostname, email address, message headers, timestamps with timezone, screenshots, logs, malware samples or hashes, redirect chain, source and destination IPs, transaction details, or other evidence relevant to the issue.

For spam reports, include full email headers and message body where possible. For phishing or malware reports, include the exact URL and evidence of the malicious behavior. For attacks, include logs showing source IP, destination IP, ports, timestamps, and attack pattern.

Incomplete reports may take longer to review. Reonr may request more information unless the available evidence already shows urgent harm.

Report phishing, malware, botnets, credential theft, spam, scams, payment fraud, unauthorized access, server compromise, network attacks, DDoS activity, illegal content, copyright abuse, trademark abuse, resource abuse, public proxy abuse, scraping abuse, open relays, exposed data, or other harmful activity involving Reonr-hosted resources.

If the issue involves a domain registered or managed through Reonr but not hosted on Reonr infrastructure, it may be handled under the Domain Abuse Policy instead of this Hosting Abuse Policy.

Reonr prohibits hosting or facilitating phishing pages, fake login pages, credential harvesters, fake payment pages, impersonation pages, deceptive forms, fake support portals, malicious redirects, or infrastructure used to collect credentials, payment data, authentication tokens, personal data, or identity documents without authority.

Reonr may disable the affected URL, website, account, mailbox, DNS record, server, or service where phishing is confirmed or strongly indicated by evidence.

Reonr prohibits malware distribution, ransomware, spyware, trojans, droppers, exploit kits, web shells, malicious JavaScript, botnet command and control, malicious redirects, drive-by downloads, fake updates, infected archives, and other harmful code.

A customer may be responsible for malware even where the malware resulted from outdated software, compromised plugins, weak passwords, exposed credentials, vulnerable themes, insecure file permissions, or third-party scripts.

Reonr may quarantine files, disable scripts, suspend sites, restrict outbound traffic, block mail, require cleanup, or terminate services where malware creates risk.

Reonr prohibits spam, unsolicited bulk email, purchased-list campaigns, harvested-list campaigns, phishing mail, malware mail, deceptive headers, spoofed sender identity, open relays, mail bombing, newsletter abuse, and mail sent in violation of applicable law or provider rules.

Customers must maintain proper sender authentication, lawful recipient consent, unsubscribe handling where required, bounce processing, list hygiene, and reasonable sending volume.

Reonr may throttle, block, suspend, or disable outbound mail where email abuse threatens IP reputation, customer deliverability, provider relationships, or public users.

Reonr prohibits denial-of-service attacks, distributed denial-of-service attacks, reflection attacks, amplification attacks, brute-force attacks, credential stuffing, unauthorized scanning, unauthorized vulnerability testing, port scanning, exploit attempts, packet floods, and unauthorized access attempts.

Reonr may null-route IP addresses, firewall traffic, suspend servers, disable accounts, or coordinate with upstream providers where network abuse threatens service stability or third-party networks.

Resource abuse includes excessive CPU, memory, disk I/O, database load, network traffic, processes, file count, mail volume, storage, backup usage, or automation that harms Reonr infrastructure, upstream providers, or other customers.

Examples include crypto mining, scraping farms, mass mailing, public file mirrors, backup dumping, abusive cron jobs, proxy networks, runaway scripts, unmanaged bots, and workloads unsuitable for the purchased service.

Reonr may throttle resources, disable scripts, request optimization, require upgrade, move workloads, suspend services, or terminate abusive usage.

Reonr prohibits content involving child sexual abuse material, credible threats of violence, terrorism-related content, human trafficking, unlawful controlled substances, illegal weapons trafficking, stolen credentials, stolen payment data, identity theft material, extortion, blackmail, revenge abuse material, illegal gambling, counterfeit goods, and other unlawful or seriously harmful content.

Reonr may take immediate action and may report serious harmful content to appropriate providers, regulators, or authorities where required or permitted by law.

Copyright, trademark, counterfeit, software piracy, illegal streaming, unauthorized downloads, and other intellectual property complaints may be handled under this Policy and the Copyright / Takedown Policy.

Reporters should provide the allegedly infringing URL, rights claimed, evidence of ownership or authority, and a clear explanation of the complaint. Reonr may forward complaints to the customer unless prohibited by law or risk.

Reonr prohibits fake shops, impersonation, investment fraud, romance fraud, payment fraud, chargeback schemes, fake invoices, fake support channels, identity fraud, counterfeit sales, and other deceptive commercial activity.

Where fraud is reported, Reonr may review hosting records, payment records, order details, customer identity signals, domain patterns, complaint evidence, and upstream provider reports.

Customers are responsible for securing and cleaning compromised websites, servers, mailboxes, databases, control panels, plugins, themes, applications, scripts, and credentials.

Reonr may require password resets, software updates, malware cleanup, file removal, DNS changes, mailbox cleanup, account isolation, customer suspension, or migration before reinstating affected services.

If a customer cannot or will not remediate compromise, Reonr may keep the affected service suspended or terminate the service to protect infrastructure and third parties.

Resellers are responsible for abuse involving their customers, sub-accounts, hosted domains, mailboxes, websites, applications, and users.

Reonr may require a reseller to suspend a customer, remove content, provide customer contact details where permitted, clean malware, stop outbound mail, or take other action. Failure by a reseller to act may result in action against the reseller account.

Reonr reviews abuse reports based on evidence, severity, affected service, customer history, public harm, infrastructure risk, provider requirements, legal obligations, and technical feasibility.

Reonr may confirm the affected resource, classify the report, validate evidence, notify the customer, request remediation, take direct mitigation, escalate to a provider, or close the report where evidence is insufficient.

Where appropriate, Reonr may notify the customer and request correction. The response time may depend on severity. Active phishing, malware, child safety issues, network attacks, or major spam incidents may require immediate action.

Customers must respond promptly, provide remediation steps, remove abusive content, patch software, clean malware, stop abusive traffic, reset credentials, or provide evidence that the report is incorrect.

Mitigation may include warning, ticket request, file quarantine, script disablement, outbound mail block, rate limit, firewall block, password reset, malware cleanup request, DNS disablement, website suspension, account suspension, server suspension, IP null-route, domain lock, service termination, or provider escalation.

Reonr will choose mitigation based on the risk and evidence. Reonr is not required to use the least disruptive action where immediate harm, provider risk, or legal risk requires stronger action.

Reonr may act without prior notice where needed to stop active phishing, malware, spam outbreaks, network attacks, data exposure, child safety risk, fraud, imminent harm, legal risk, provider escalation, infrastructure instability, or serious abuse.

Emergency action may interrupt websites, email, DNS, servers, databases, backups, control panel access, or related services.

Reonr may preserve logs, files, account records, support records, DNS records, mail records, payment records, server data, and other evidence where reasonably necessary for abuse handling, security, legal compliance, provider requirements, dispute handling, or enforcement.

Preservation does not guarantee that all data is available, complete, unchanged, or retained indefinitely. Customers remain responsible for their own backups and evidence preservation.

Reonr may share relevant information with data centers, network providers, security vendors, payment gateways, registrars, registries, law enforcement, regulators, affected parties, or professional advisers where required or permitted by law, provider rules, policy enforcement, or protection of rights and safety.

Upstream providers may require Reonr to suspend, restrict, null-route, terminate, or otherwise mitigate abuse within a short timeframe. Reonr may act to preserve provider relationships and network stability.

Reonr may decline reports that are unsupported, vague, inaccurate, unrelated to Reonr resources, abusive, automated without evidence, or submitted to harass a customer.

Knowingly false reports, forged evidence, repeated abusive reporting, or attempts to misuse the abuse process may be ignored, blocked, or treated as abuse.

Repeated abuse, repeated compromise, repeated spam complaints, repeated malware infections, repeated ignored notices, repeated provider escalations, or repeated policy violations may result in stronger action, including permanent termination or refusal of future service.

Reonr may treat related accounts, reseller sub-accounts, repeated payment patterns, repeated domain patterns, or accounts under common control as connected where needed to prevent abuse evasion.

Reinstatement may require cleanup, evidence of remediation, password resets, software updates, customer removal, DNS correction, mail configuration changes, verification, payment correction, provider approval, or written assurance that the abuse will not continue.

Reinstatement is not guaranteed. Reonr may refuse reinstatement where abuse is severe, repeated, unlawful, fraudulent, provider-restricted, or creates unacceptable risk.

Customers may be responsible for costs caused by abuse or compromise, including cleanup fees, restore fees, emergency support, incident response, provider fees, chargeback fees, IP reputation recovery, domain recovery, manual work, or other costs incurred by Reonr.

Payment of fees does not guarantee reinstatement where the abuse risk remains unacceptable.

Reonr handles personal data in abuse reports and investigations according to the Privacy Policy and applicable law. Abuse handling may require processing account data, logs, IP addresses, message headers, support records, payment records, and technical evidence.

Reonr may disclose relevant information where required or permitted for security, legal compliance, provider requirements, abuse mitigation, dispute handling, or protection of rights and safety.

This Policy should be read with the Terms of Service, Acceptable Use Policy, Domain Abuse Policy, Copyright / Takedown Policy, Privacy Policy, Refund Policy, and any service-specific rules.

Where a specific policy gives more detailed rules for a specific issue, that policy applies together with this Hosting Abuse Policy.

Reonr may update this Hosting Abuse Policy from time to time to reflect legal, security, provider, technical, operational, or business changes. The updated version will be posted with a revised Last Updated date.

Continued use of services after changes take effect means you accept the updated Policy.

Business address: Port Harcourt, Rivers, Nigeria.

Hosting abuse reports should be sent to [email protected]. Legal notices and policy questions should be sent to [email protected]. Support requests and general account issues should be sent to [email protected]. Privacy requests should be sent to [email protected].

Contact should be made by email through the channels listed in this section unless Reonr provides a different channel for a specific service, dispute, or legal process.