Understand the service before changing the system.

Find the operating account behind an existing .ng address

NiRA describes a registry, registrar and registrant model for .ng domains. A Nigerian organisation may recognise its public web address without knowing which registrar manages it or who controls the recovery route. A takeover should establish that operating picture before a redesign creates additional dependencies.

We assess the agreed website or application, observed failures and available access. The enquiry can begin with a public URL and a description; credentials and customer records stay out of the public form.

Distinguish the services that must continue

Identify domain management, hosting, deployment, email and external provider arrangements. They may have different owners. The organisation needs to know which account and responsible person can authorise a change, rather than assuming that the person who edits a page controls every dependency.

A registrar's actual process determines a domain-related action. We do not claim NiRA registrar status or promise an unverified transfer or recovery.

Choose a repair with a reversible review route

Use one important customer task and its observed failure to set the first scope. Check the proposed result in an appropriate test environment and record how to recover if the change is unsuitable. A working homepage alone does not prove that enquiry, email or payment dependencies survived.

The handover names verified ownership, unresolved access and supported editing operations. Ongoing response arrangements and specialist security work require explicit scope. The result should make the organisation better able to continue its own service.

Reference: NiRA .ng FAQ. Describe the service your users can no longer complete.