Frequently asked questions

Choose the namespace that matches your organisation and intended use, then apply through an approved registrar partner. The registrar validates your details and submits the registration through the registry channel.

Evidence depends on the namespace. It may include incorporation records, sector authorisation, public-interest status, or proof that the requested name relates to the applicant. Your registrar will confirm the applicable checklist.

A .biz.ng name is registered through the registrar channel and remains subject to the registry’s eligibility and acceptable-use rules. A WHOIS result does not reserve a name or replace the application review.

The lookup service returned no matching registration record. This does not reserve the name or establish that it can be registered. A service failure, unsupported namespace or restricted response is shown separately.

A registrar is the registrant’s primary service channel. It collects and validates application information, submits registry transactions, manages renewals and transfers, and provides first-line support.

Renewals are managed through the sponsoring registrar. Contact the registrar before the expiry date shown in registry data and allow enough time for payment, eligibility revalidation, or account recovery.

Eligible domains may be transferred in line with registry policy and applicable status locks. Begin with the receiving registrar, who will confirm the required authorisation and whether any hold or dispute prevents transfer.

Enter the complete domain, such as example.biz.ng, in the WHOIS lookup. The result can show lifecycle status, dates, nameservers, DNSSEC information, and the sponsoring registrar when the registry source provides them.

Public lookup responses focus on operational registration data. Personal contact details may be redacted or omitted. A missing field does not establish availability or technical configuration.

Ask your sponsoring registrar to correct registration details. Contact the registry where the issue concerns information held by Enterprise IT or a registry-level escalation.

Follow the process in the Registration Data and RDAP Policy. Each request is assessed under the applicable rules; submitting a request does not guarantee disclosure.

Use the abuse reporting form. Include the affected managed domain, accurate URLs or indicators, a clear incident statement, and relevant evidence. Submit one report for related activity.

You receive a case code. The compliance desk triages the report, validates the evidence, investigates with the appropriate parties, and records reporter-visible updates. Use the tracking page with the case code and reporter email.

Domain disputes are assessed under the applicable registry terms, acceptable-use requirements, and any recognised dispute process. Send the registry desk the domain, parties involved, supporting documents, and details of any active proceeding.

The Legal Hub provides the Acceptable Use Policy, Terms of Service, and Privacy Policy. Use the version and last-updated information shown on each document when reviewing obligations.

.col.ng is for collectives, collaboration and collaborative learning. It gives communities, teams and shared projects an online identity for working, connecting and learning together.

Individuals and organisations can apply, including people setting up or representing a collective, community, team or learning project. Registration remains subject to the applicable terms, naming rules and acceptable-use policy.

No. College status or educational accreditation is not a blanket condition of .col.ng registration. Registration does not accredit an institution, approve a course or recognise a qualification.

Yes. Study circles, peer-learning groups, mentoring communities, collaborative research projects and tutor-led learning communities are within the intended scope, subject to the registration terms and lawful use. Any approvals required for the underlying activity remain the operator's responsibility.

Yes. Commercial and non-commercial collaborative uses are supported. Domain registration does not remove any obligations applying to your organisation, services or activities.

Yes. An individual can register while establishing a project or community, subject to the normal registration rules. Keep the registrant information accurate and agree how responsibility will be transferred if the project later changes hands.

Identify the responsible individual or organisation and agree the management arrangement before registration. Keep authorised contacts current and use your registrar's applicable change or transfer process when responsibility changes.

Not by default. Website hosting, email, member platforms and learning applications are separate services unless a registrar explicitly includes them in an offer.

An existing registration is not cancelled or forced to move simply because the namespace's positioning broadens. Existing registrations remain subject to their applicable terms. Contact your registrar about any registration-specific question.

.ote.ng is an open commercial namespace for development, testing and evaluation. OTE stands for Operational Test and Evaluation. Individuals and organisations can use it for staging, prototypes, demos and other development workflows under the applicable terms.

No. Registrar accreditation or membership of a testing programme is not a general customer registration requirement. Use a participating registrar channel for an actual registration.

Yes. Customer registrations are governed by their commercial registration terms. They are not simulated test objects that disappear when an application or sandbox is reset.

Yes, subject to maintaining the registration under its terms. Persistent staging, demos and technical documentation remain intended uses; a product launch does not itself force a domain change.

Not by default. Hosting, DNS services, email, certificates and development platforms are separate unless explicitly included in a registrar's offer.

No. Site operators choose appropriate access and indexing controls. Use authentication for confidential systems. A deliberately public demo or documentation site can be made discoverable.

No. Configure the relevant provider's test environment and credentials. The domain suffix does not prevent real payments or outbound messages.

No. A .ote.ng registration does not by itself reserve the corresponding label under another suffix. Check any separate registration through the applicable registrar and rules.

Yes. A group might use .col.ng for its community and learning identity, and a separately registered .ote.ng name for development exercises, prototypes or demos. Each registration and any connected services remain separate.

Enterprise IT manages a portfolio of nine .ng namespaces. The registry maintains registration records and policies and works with registrar partners on the services enabled for each namespace.

The portfolio comprises biz.ng, ltd.ng, plc.ng, ngo.ng, col.ng, gen.ng, one.ng, ind.ng and ote.ng. Visit Domain extensions to compare their intended uses and requirements.

NiRA manages the .ng country-code top-level domain. Enterprise IT operates a separate private registry service within its listed second-level namespaces. The applicable registration agreement and registry policies govern a registration in those namespaces.

Registrations are handled through registrar partners. This website provides namespace information, registration guidance, public lookup and registry support.

gen.ng supports general-purpose registrations under the applicable registration and acceptable-use rules. Ask your registrar to confirm that your planned business or digital project meets those requirements.

one.ng serves brands, projects and individuals under the applicable registration rules. Evidence of identity or entitlement to the requested name may be required. Your registrar will explain the requirements for your application.

No. Registration establishes the right to use the domain under the applicable terms. It is not professional accreditation or verification of every claim made on a website.

Your registrar supplies the current registration and renewal offer. Confirm the term, currency, taxes and any additional or premium charges before accepting it. Registry wholesale charges and registrar retail prices may differ.

Not necessarily. The relevant quote or schedule must explain the initial charge and renewal treatment. Do not infer the renewal amount from the registration price.

Some fields may be withheld for privacy, unsupported by the service or absent from the returned data. A missing field does not establish a domain's availability or technical configuration. A failed lookup should be shown separately as a service error.

Contact your registrar first for billing, renewals, transfers and account access. Contact the registry for its public lookup service, namespace policies or registry-level escalation. Use the separate abuse route for suspected misuse.