.ng WHOIS Lookup
.ng is the country-code extension of Nigeria, administered by NiRA. This page explains which details the record contains.
- 1.494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address 216.73.216.31
.ng WHOIS Lookup: NiRA Records and Their Fields
.ng is the country-code extension of Nigeria, delegated into the root zone on 15 March 1995 and operated by the Nigeria Internet Registration Association. Queries are answered by whois.nic.net.ng on port 43, and in our measurement on 12 August 2026 the reply carried twenty fields. IANA's list holds an RDAP address for the extension, but that endpoint timed out during the measurement, and the zone carries a DS record in the root.
The widest section of the reply belongs to the registrar. In the record we measured, the organisation's name was followed by its street address, city, state, country, phone number and email on separate lines, with a second email and phone added for abuse reports. On the registrant side there is a single line, and it holds not a name but the identifier of an object in the registry database. The record describes the party that sold the name in detail while never naming the party that took it.
The calendar and the locks are in the reply as well. In the sample we measured, creation fell in 2009 and the expiry date in 2099; the status lines said the name was active and that updates and deletion were closed, and those two codes carried the server prefix, meaning the registry applied them. For another extension using second-level categories in the same way, see .com.tr WHOIS lookup; for one that keeps far wider identity blocks, .my WHOIS lookup.
About the .ng extension
- Extension
- .ng
- WHOIS server
- whois.nic.net.ng
- RDAP endpoint
- https://rdap.nic.net.ng
- Registry
- Nigeria Internet Registration Association (NiRA)
- Delegated
- 15 March 1995
- Measured field count
- 20 fields (12 August 2026)
- Registrar block
- Street address, city, state, country, phone and email all arrive open
- Registrant
- An internal identifier only; no name or contact line
WHOIS FAQ
Why is there no registrant name in a .ng record?
Because the registry does not publish that field. In our measurement on 12 August 2026 the reply held only an identifier for the registrant; no name, address or contact line was opened. The details of the organisation that sold the name, by contrast, were written out at length. That is why the counterpart for questions of identity is the registrar, whose phone number and email the reply also provides.
What is in the registrar block of a .ng record?
In the record we measured, the block carried the organisation's name, street address, city, state, country, phone number and email, plus a separate email and phone line for abuse reports. That width is unusual: most registries give only a name and an IANA number. Here, when you need to report a problem, you do not have to go looking for an address — the record hands it to you.
What is the identifier in a .ng record used for?
It distinguishes objects in the registry database. In the record we measured there was one number for the record itself and another for the registrant, both ending with the abbreviation of the registry. The identifier is stable: it stays the same even as details in the record change. But it is only a label — it carries no name, address or contact data, and on its own it verifies nothing about identity.
Why does a .ng expiry date read 2099?
The record we measured belonged to the registry's own service name, and its expiry had been set to the year 2099. Registries use distant dates like this to keep their infrastructure names clear of any risk of running down. Do not expect such a date on an ordinary address, where the value shows the real end of the paid term. The date itself is a hint about who holds the record.
Does the RDAP endpoint work for the .ng extension?
The address is registered, but no answer came back in our measurement. IANA's bootstrap list holds an RDAP address for .ng, and the query we sent to it on 12 August 2026 timed out. So a second channel is defined but was not reachable at that moment. The dependable route for registration data is the server on port 43, which returned a complete reply in the measurement.
What do the status codes in a .ng record mean?
The record we measured carried three status lines: the name was active, while updates and deletion were closed. The latter two codes carried the server prefix, which says the registry applied the lock and the registrar cannot lift it. Where a code carries the client prefix, the authority sits with the registrar. When an operation bounces, the prefix shows which party to approach.