A complete document pack helps us understand your institution, the requested domain and the authority behind the application. Use this guide when preparing a restricted educational or government .ng request with us. It is our practical submission checklist, not a replacement for the registry's eligibility rules.
IN THIS ARTICLE
01 Start with the correct application guide
Read Our .edu.ng requirements and sample letter, Our .gov.ng requirements and sample letter, or Our .sch.ng guide as appropriate. Confirm the institution type before paying for a name on the assumption that it will be approved.
02 Prepare one consistent set of documents
- Application identity: use the same legal or official institution name throughout. Explain abbreviations and name changes with relevant evidence rather than silently using different names.
- Requested domain: write the exact proposed name consistently. A government entity may require a particular namespace level, so confirm it before signing.
- Eligibility evidence: include the relevant institutional approval, accreditation or governmental clearance. A contact letter alone does not prove eligibility.
- Signed authority: use genuine institutional letterhead and an appropriate real signatory. Include complete contact details for verification.
- Technical preparation: confirm the intended nameservers and who will manage website and email setup after approval.
03 Make the files easy to review
Scan complete pages with readable text, dates, letterhead and signatures. Avoid photographs with glare or cropped edges. Give the files descriptive names, for example institution-authorisation-2026-10-06.pdf and institution-approval-reference.pdf. These are naming examples, not required registry filenames.
Do not edit a signed scan to replace an officer or domain name. Prepare a corrected document and have the authorised signatory review it again. Keep the earlier version for your own records so the change can be explained.
04 Submit through your support case
Open an authenticated ticket and identify the proposed domain and order reference where available. Follow our instructions for attaching or securely providing the files. Do not upload institutional documents into a public website folder to create a download link.
We are applying for [domain] on behalf of [institution]. Our institution type is [type]. Attached are the signed authorisation and [approval evidence]. Please confirm any missing information before the application is submitted.
That example is a useful introduction to your case. It does not replace the signed letter. Do not include hosting passwords, private keys, payment-card details or unrelated personal records.
05 Respond to clarification in the same case
Keep the institutional and technical contacts reachable. When we request a correction, refer to the original request and describe what changed. Avoid opening parallel applications with different domain spellings or officers unless the handling team specifically instructs you to do so.
06 Questions we receive
Can we submit the letter first and the evidence later?
You can ask us to review what you have, but an incomplete pack may not be ready for submission or approval. Tell us which documents remain outstanding rather than presenting the request as complete.
Does ordering hosting reserve or approve the domain?
Hosting and restricted-domain approval are different processes. Ask us about your proposed project before scheduling a launch that depends on verification.