.info WHOIS Lookup
.info is a generic extension operated by Identity Digital. Registration data arrives over RDAP; look up a .info address and see what the record holds.
- 1.494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address 216.73.216.31
.info WHOIS Lookup: Identity Digital Records
.info is a generic extension delegated into the root zone on 26 June 2001 and operated by Identity Digital Limited. The zone carries a DS record in the root, so it is signed with DNSSEC. One detail stands out: the WHOIS server field in IANA's .info record is empty. In our measurement on 12 August 2026, a query for a .info name sent to the extension's former WHOIS address came back as a single line — TLD is not supported. Port 43 no longer returns registration data here.
The data has not disappeared; the channel has changed. Identity Digital publishes the same record at its RDAP endpoint, rdap.identitydigital.services, and in the measurement that endpoint answered without trouble. The record it returned carried registration, expiration, transfer and last-changed events alongside a registrar role. This is what ICANN's transition policy, in force since 28 January 2025, looks like in practice: WHOIS stopped being mandatory for generic extensions and RDAP became the authoritative source.
The consequence for you is simple: if an older WHOIS tool returns an empty or broken answer for .info, the problem is the tool and not the domain. Our lookup picks the correct channel for each extension automatically, so the result screen still shows the dates, the registrar and the status codes as usual. To compare against a generic extension that still keeps port 43 open, the .org WHOIS lookup page shows that measurement.
About the .info extension
- Extension
- .info
- 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
- Identity Digital Limited
- Delegated
- 26 June 2001
- Port 43 status
- Closed — returned "TLD is not supported" in the 12 August 2026 measurement
- Source of record data
- rdap.identitydigital.services
- RDAP events
- registration, expiration, transfer, last changed
WHOIS FAQ
Why does a .info WHOIS lookup return no result?
Because the port 43 WHOIS service has been shut down for this extension. The WHOIS server field in IANA's .info record is empty, and in the 12 August 2026 measurement a query to the former address returned only TLD is not supported. The server is saying it does not recognise the extension at all, not that the name could not be found. Tools that conflate the two show a registered name as available; the correct channel is RDAP.
How does .info registration data arrive over RDAP?
Identity Digital publishes the record as JSON at rdap.identitydigital.services. Our lookup recognises the extension and goes straight to that endpoint, so there is no extra step for you. The reply in our measurement carried registration, expiration, transfer and last-changed events. JSON is far more reliable to parse than plain text: field positions are fixed, and a registry changing its text template cannot break the result.
Are the creation and expiry dates visible for a .info domain?
They are. In an RDAP reply the dates arrive as separate event records: registration for the creation date, expiration for the end date and last changed for the most recent edit. All three were present in the 12 August 2026 measurement, together with a transfer event. Our result screen maps them onto the date fields and calculates the time remaining, so closing port 43 costs you no date information.
Does a .info lookup include the registrant's name?
Not at registry level. The only role present in the RDAP reply we measured was the registrar; no registrant identity or contact block was opened. That is not a shortcoming of the protocol but the result of the publication policy that settled across generic extensions after 2018. RDAP does improve on WHOIS here in one respect: it is designed for authenticated, tiered access, so a separate level can be defined for authorised parties.
With port 43 closed, is the .info result still reliable?
It is, and for parsing it is actually sturdier. The data comes from the same registry database; only the protocol carrying it has changed. Because an RDAP reply is structured, the risk of fields being mismatched is lower than with free-form text. On our side a result is cached for six hours when the name is registered and five minutes when it looks available — those windows are the same whichever channel supplied the data.
Does the .info extension support DNSSEC?
It does. A DS record for .info exists in the root zone and we confirmed it in the 12 August 2026 measurement, so the zone is signed. That is a fact about the extension; whether an individual domain is signed is a separate question that depends on the DS record for that specific name. We show the two separately in the result so that a signed zone is never mistaken for a signed address.