Domain Abuse Policy

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

Domain abuse can harm victims, domain registrants, registries, registrars, hosting providers, payment systems, brand owners, and internet users. Reonr may act where domain-related activity creates security, legal, infrastructure, provider, or public harm risk.

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

This Policy applies to domain registration, domain transfer, domain renewal, domain restoration, DNS management, nameservers, DNS records, domain contacts, domain privacy or protection services, domain add-ons, and domain-related services ordered or managed through Reonr.

It applies whether the domain points to Reonr hosting, third-party hosting, a parking page, a redirect, mail infrastructure, a content delivery network, or another provider.

Hosting, server, website, file, email, and infrastructure abuse may also be handled under the Hosting Abuse Policy or Acceptable Use Policy.

Reonr may act as a domain reseller, domain service provider, DNS provider, hosting provider, support provider, or billing provider depending on the specific domain and service.

Some domain actions can only be performed by the sponsoring registrar, registry, or domain authority. Reonr may need to escalate reports or follow instructions from a registrar, registry, ICANN, NiRA, country-code registry, court, law enforcement, or other lawful authority.

For generic top-level domains, registrar and registry responses may be affected by ICANN DNS abuse mitigation requirements. For .ng domains, registry and registrar action may be affected by NiRA policies and the applicable registrar relationship.

Reonr's ability to act may depend on domain status, registrar tools, registry rules, evidence quality, legal authority, provider requirements, and whether the domain is registered, hosted, or DNS-managed through Reonr.

DNS abuse includes domain-related activity involving malware, botnets, phishing, pharming, and spam when spam is used to deliver or enable those other abuse types.

DNS abuse may involve the domain name itself, subdomains, nameservers, DNS records, redirects, mail records, parked pages, or domain infrastructure used to support harmful activity.

Reonr may prioritize well-evidenced DNS abuse because registrars and registries may require clear evidence before applying domain-level mitigation.

Not every complaint about website content is domain abuse. Some issues are hosting abuse, copyright disputes, trademark disputes, consumer disputes, defamation claims, business disputes, or content moderation issues.

Where Reonr only provides domain registration and not hosting, Reonr may not be able to remove website content. In those cases, Reonr may direct the reporter to the hosting provider, content platform, registrar, registry, court, law enforcement, or relevant dispute process.

Reonr prohibits domains used for phishing, fake login pages, fake payment pages, credential harvesting, fake support portals, impersonation, malicious redirects, or schemes that trick users into giving credentials, payment information, personal data, or identity documents.

A phishing report should include the exact URL, screenshots, brand impersonated, timestamps, redirect chain where available, and evidence showing how the domain is used to deceive users.

Reonr prohibits domains used to distribute malware, ransomware, spyware, trojans, droppers, exploit kits, malicious scripts, fake updates, botnet command and control, botnet rendezvous, malicious downloads, or other harmful code.

Reports should include malware URLs, hashes, analysis links, timestamps, command-and-control indicators, DNS records, redirect chains, screenshots, or other technical evidence where available.

Reonr prohibits unauthorized manipulation of DNS, nameservers, registrant accounts, transfer settings, authorization codes, or domain records to redirect users, steal traffic, impersonate services, or take control of a domain without authority.

Domain hijacking and transfer disputes may require identity verification, registrar review, registry escalation, transfer policy review, court order, or involvement of the sponsoring registrar.

Spam may be treated as domain abuse where the domain is used to deliver, advertise, redirect to, or support phishing, malware, botnets, pharming, credential theft, or other harmful activity.

Spam reports should include full email headers, message body, sending domain, return-path, links, timestamps, source IPs, and the specific domain or subdomain involved.

Reonr may review domains used for fake shops, investment fraud, romance fraud, payment fraud, identity fraud, government or business impersonation, counterfeit sales, fake invoices, fake support, or other deceptive activity.

Some impersonation or trademark disputes may require rights-holder evidence, registrar review, registry process, court order, UDRP, local dispute process, or other formal dispute mechanism.

Domain registrants must provide accurate and current registrant, administrative, technical, billing, and contact information as required by registrar, registry, ICANN, NiRA, country-code registry, and other domain authority rules.

Inaccurate, false, unreachable, or fraudulent domain contact information may result in verification requests, domain hold, suspension, cancellation, transfer restrictions, or escalation to the registrar or registry.

Trademark, brand, copyright, counterfeit, and domain name disputes may not always be domain abuse. Reonr may require evidence of rights, evidence of misuse, exact URLs, screenshots, and a clear explanation of the requested action.

Some disputes may need to be resolved through the domain's applicable dispute process, court order, registrar process, registry process, UDRP, local dispute process, or other formal mechanism. Reonr may not transfer, cancel, or suspend a domain based only on an unsupported ownership dispute.

Reonr may review domains used for child sexual abuse material, credible threats of violence, terrorism-related content, human trafficking, illegal weapons trafficking, unlawful controlled substances, stolen credentials, stolen payment data, identity theft, extortion, blackmail, illegal gambling, or other unlawful activity.

Serious illegal or harmful activity may be escalated to registrars, registries, providers, regulators, or law enforcement where required or permitted by law.

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

Include the domain name, subdomain, exact URL, abuse type, evidence, timestamps, screenshots, redirect chain, DNS records, email headers, logs, malware analysis, or other details that help Reonr identify the issue.

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].

Well-evidenced reports can usually be reviewed faster. Evidence should identify the specific domain or subdomain, show the current or recent abusive behavior, and explain why the behavior is domain abuse.

Reports based only on suspicion, general reputation, unsupported allegations, business disputes, search results, or old cached content may be insufficient for domain-level action.

Reonr may ask for additional information before acting unless urgent harm requires immediate mitigation.

WHOIS and RDAP records may not show all domain registration data because of privacy laws, registry rules, registrar practices, proxy services, or redaction requirements.

Reonr may use internal account records, registrar records, registry data, DNS data, support records, payment records, and public WHOIS/RDAP records when reviewing domain abuse.

Requests for non-public registration data may require lawful basis, identity verification, registrar process, registry process, legal authority, or other requirements under applicable policy and law.

Reonr reviews domain abuse reports based on evidence, severity, domain status, customer history, domain authority rules, registrar tools, registry requirements, hosting relationship, provider requirements, public harm, and legal obligations.

Reonr may classify the report, verify the domain relationship, review DNS records, check hosting status, notify the registrant, request remediation, take direct action if available, escalate to a registrar or registry, or close the report if evidence is insufficient.

Where appropriate, Reonr may notify the registrant or customer and request correction, evidence, contact verification, DNS changes, hosting changes, removal of harmful content, domain configuration changes, or other remediation.

The response time may depend on severity. Active phishing, malware, botnet, pharming, child safety, fraud, or major public harm may require immediate action without prior notice.

Depending on evidence and authority, Reonr may warn the registrant, request correction, disable DNS, change nameservers, remove DNS records, lock the domain, place the domain on hold, suspend domain services, restrict transfers, disable domain add-ons, preserve evidence, or escalate to the sponsoring registrar, registry, or lawful authority.

Some actions may only be available to the sponsoring registrar or registry. Reonr may forward evidence or request action from the party with authority to mitigate the abuse.

Reonr may take urgent action without prior notice where needed to stop active phishing, malware, botnet command and control, pharming, child safety risk, fraud, domain hijacking, credential theft, registry escalation, provider escalation, legal risk, or serious public harm.

Urgent domain action may interrupt websites, email, DNS, redirects, domain parking, nameserver service, domain management, or related services.

Reonr may escalate reports, evidence, account details, domain data, or technical information to registrars, registries, ICANN, NiRA, country-code registry operators, data centers, security vendors, law enforcement, regulators, or professional advisers where required or permitted by law, provider rules, domain policy, or protection of rights and safety.

Registrars and registries may impose their own response timelines, evidence requirements, verification steps, hold statuses, suspension rules, or dispute processes. Reonr may need to follow those requirements before action can be completed.

If a domain registered or managed through Reonr points to third-party hosting, Reonr may not control the website files, server, application, or content. Domain-level action may still be considered where the domain itself is used for well-evidenced abuse.

For content hosted elsewhere, reporters may also need to contact the hosting provider, CDN, platform, payment provider, registrar, registry, court, or law enforcement depending on the issue.

Reonr handles personal data in abuse reports and domain investigations according to the Privacy Policy and applicable law. Domain abuse handling may require processing registrant data, account data, DNS data, payment records, support records, IP addresses, WHOIS/RDAP data, and technical evidence.

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

Reonr may preserve domain records, DNS records, account data, payment records, support records, abuse reports, logs, registrar responses, registry responses, and other evidence where reasonably necessary for abuse handling, legal compliance, provider requirements, dispute handling, or enforcement.

Preservation does not guarantee that all data is available, complete, unchanged, or retained indefinitely.

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

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

Reinstatement may require remediation, evidence of cleanup, DNS changes, hosting changes, contact verification, identity verification, registrant data correction, payment correction, registrar approval, registry 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, registry-restricted, registrar-restricted, or creates unacceptable risk.

Repeated abuse, repeated phishing, repeated malware, repeated inaccurate registrant data, repeated ignored notices, repeated provider escalations, repeated domain patterns, or repeated policy violations may result in stronger action, including termination, refusal of future domain orders, cancellation where allowed, or escalation to registrars and registries.

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

Customers may be responsible for costs caused by domain abuse or domain compromise, including recovery fees, restore fees, registry fees, registrar fees, emergency support, manual review, incident response, provider fees, chargeback fees, legal handling costs, and other costs incurred by Reonr.

Payment of fees does not guarantee reinstatement where the domain abuse risk remains unacceptable or where registrar, registry, provider, or legal restrictions apply.

This Policy should be read with the Terms of Service, Acceptable Use Policy, Hosting Abuse Policy, Copyright / Takedown Policy, Privacy Policy, Refund Policy, and any domain-specific registry or registrar rules.

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

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

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

Business address: Port Harcourt, Rivers, Nigeria.

Domain 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.