Dispute Resolution Policy

This policy explains how Enterprise IT handles competing rights, eligibility complaints, and requests to review registry action. It applies to managed subdomains under the Terms of Service.

Send the full domain, your identity and authority, a reachable contact, the conduct or decision challenged, the rights relied on, dated evidence, and the remedy requested to the compliance desk.

Identify related proceedings and material facts, including any legitimate relationship between the parties. False allegations or omitted evidence may affect assessment. Do not send passwords or irrelevant personal data.

Enterprise IT checks whether the domain is managed by it, whether the complaint is sufficiently supported, and whether another forum must decide the matter. A registry complaint does not itself establish infringement or entitlement.

For alleged abusive registration, relevant considerations include similarity to established rights, the registrant’s legitimate interest, and evidence of bad-faith registration or use. These considerations guide assessment; this service is not represented as an ICANN UDRP tribunal.

Where appropriate, the registrar or registrant receives the substance of the complaint and a stated response deadline. The recipient may supply authority evidence, a legitimate-use explanation, corrections, or evidence rebutting the allegation.

A response period depends on urgency and the applicable procedure and will be stated in the notice. Reasonable requests for additional time are considered. Emergency protective action may precede notice where ongoing harm requires it.

A transfer or registrant-change restriction may preserve the subject of a dispute. A DNS hold may be used where continued resolution creates a substantiated risk under the AUP. Restrictions should be proportionate to the issue.

Parties remain responsible for renewal. A dispute does not automatically extend a registration, guarantee restoration, or decide responsibility for fees. Relevant evidence may be retained under a legal hold.

The registry may reject an unsupported complaint, request correction, maintain or remove a restriction, facilitate an agreed settlement, or implement a binding decision. A complex ownership dispute may require determination by a competent court or applicable dispute provider.

Transfer or cancellation requires a sufficient contractual, legal, or consensual basis. The registry does not award damages through this process. Notices explain the outcome, implementation conditions, and available review route where disclosure is permitted.

A party seeking internal review should promptly identify the alleged error and provide new or previously overlooked evidence, quoting the original reference. Comply with any deadline in the decision notice.

A different reviewer is used where practicable. Internal review does not prevent urgent relief or another remedy available under mandatory law. A pending challenge does not automatically stay a binding order; provide evidence of any valid stay.

NiRA’s published policies may apply where the registration or parent domain is within their scope. Consult the NiRA policy library and the competent provider’s rules before filing. Enterprise IT does not promise that every private subdomain dispute is eligible for that process.

Nigerian courts of competent jurisdiction remain available. Arbitration applies where the parties have validly agreed to it. Enterprise IT verifies legal requests and implements applicable orders, subject to lawful confidentiality and privacy obligations.

Report details may be shared only as necessary to assess the matter, permit a response, or meet legal obligations. Reporter-visible case updates do not expose internal notes or private evidence.

For an abuse case, use the reference and reporter email address at Track Abuse Report. For a rights dispute or review, follow the contact channel supplied with your acknowledgement.