.life WHOIS Lookup
.life is a generic domain extension operated by Binky Moon. Look up a .life address and see the state of its record.
- 1.494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address 216.73.216.31
.life WHOIS Lookup: What the Record Shows
.life is a generic extension delegated into the root zone on 8 May 2014; IANA's record names Binky Moon, LLC as the contract holder and leaves the WHOIS server field empty. In our measurement on 12 August 2026, port 43 returned no registration data. Queries are answered by the RDAP endpoint at rdap.identitydigital.services, and the zone carries a DS record in the root.
When we queried the registry's own name on 13 August 2026, three status codes stood in the record: deletion, transfer and updates were all closed. Each of the three carried the server prefix. That prefix names the authority — the registry set these codes and the registrar cannot lift them. Codes with the client prefix work the other way: the company that sold the name sets them and can withdraw them. The same words arrive from two different places.
This is the first line to read when you need to act on an address. With transfer closed, a move request stops at registry level rather than at the registrar; with updates closed, a name server change will not go through either. Our result screen carries the status codes as one of its eight fields, so you do not have to open the raw reply to see a lock. Run a .life lookup and check the prefix. For sibling extensions on the same endpoint, see .show WHOIS lookup and .tools WHOIS lookup.
About the .life extension
- Extension
- .life
- WHOIS server
- This extension has no WHOIS service on port 43; registration data is published over RDAP.
- RDAP endpoint
- https://rdap.identitydigital.services/rdap
- Registry
- Binky Moon, LLC — the contract holder in the IANA record
- Delegated
- 8 May 2014
- Source of record data
- rdap.identitydigital.services
- Measured status codes
- delete, transfer and update closed; all three carry the server prefix (13 August 2026)
- Measured sample
- nic.life: registered 31 January 2014, transferred 24 June 2014, expires 31 January 2027
- Unregistered name
- The endpoint answers with a separate not-found response instead of a record
WHOIS FAQ
What do the status codes in a .life record mean?
Status codes come from a shared vocabulary that states which operations a name is open to. The nic.life record we measured on 13 August 2026 carried three of them, and each closed a door: deletion, transfer and updates. A code is not a warning but a technical barrier — the registration system refuses the operation outright. Reading this line before you act on an address beats working out afterwards why a request bounced.
Who is able to lift a lock with the server prefix?
Only the registry. The prefix on a code settles the authority: codes beginning with client are set by the registrar that sold the name and can be withdrawn by that registrar, while codes beginning with server are set by the registry and the registrar cannot touch them. All three codes in the record we measured carried the server prefix. On such an address a request to your registrar leads nowhere until the party that set the lock removes it.
Can a .life domain move while transfer is closed?
Not while the lock stands. A transfer request raised for such an address is refused by the registration system itself, so the delay is not about a registrar being slow or withholding approval. Because the registry set the lock, it is also lifted at that level. Codes like these are usually a protection rather than a fault: registries keep them on their own service names and on addresses that warrant extra care.
How does an available .life name look in a lookup?
It comes back as a separate answer instead of a record. When we asked for a never-registered name on 13 August 2026, the RDAP endpoint returned not found and the result screen marked the name as available. In plain-text WHOIS every registry words this case in its own sentence; RDAP replaces the sentence with a code, which leaves nothing open to interpretation. Available results are cached for five minutes and registered ones for six hours.
Which channel supplies .life registration data?
RDAP is the only channel. IANA's .life record lists no WHOIS server, and our measurement on 12 August 2026 drew nothing from port 43; across generic extensions RDAP has been the authoritative source since 28 January 2025 in any case. The reply arrives as JSON and is parsed into eight fields: the domain name, three dates, the registrar, the name servers, the status codes and the DNSSEC state. The raw reply stays readable in its own tab.
What information is not tied to a person in .life records?
Everything touching identity is absent. The only role in our measurement was the registrar; no block was opened for a name, an address, a phone number or an email. What the record does hold describes the technical state of the domain: dates, locks and name servers. Across generic extensions, contact data belonging to natural persons has been published in masked form since 25 May 2018, so the record stands while the personal fields arrive closed.
Does a locked .life domain still reach its expiry date?
It does. The locks block deletion, transfer and updates; they do not stop the clock. The expiry date sits in the record as an event of its own and moves forward only when the domain is renewed. In the nic.life record we measured, that date was 31 January 2027. Our result screen shows the expiry date beside the status codes, and reading the two together gives you the protection and the calendar in one view.