.info WHOIS Lookup
.info is a generic extension operated by Identity Digital, and its registration data is published over RDAP. Look up a .info name to see its dates, registrar and status.
- 1,494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address
.info WHOIS Lookup: Identity Digital Records
.info entered the root zone on 26 June 2001 as a generic extension and is operated today by Identity Digital Limited, which also signs the zone with DNSSEC. IANA's record for .info lists no WHOIS server, as the registry has retired its port 43 service. Since ICANN's transition policy took effect on 28 January 2025, generic extensions no longer have to run WHOIS, and RDAP is now their authoritative source of registration data.
For .info, that source is rdap.identitydigital.services. Its reply carries dated events for registration, expiration, last change and transfer, and the only role it names is the registrar. No registrant name or contact block is included. The whois.com.tr lookup sends .info queries straight to this endpoint, so the result screen still shows the dates, the registrar, the status codes and the name servers. For a generic extension that still answers on port 43, open the .org WHOIS lookup.
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
- In the root zone since
- 26 June 2001
- Data channel
- RDAP (rdap.identitydigital.services); port 43 retired
- Not published
- Registrant name and contact details
- Last checked
- 12 August 2026
Looking for whether a name is still free, rather than who holds it? run a domain name search
WHOIS FAQ
Why does my WHOIS tool return nothing for a .info domain?
Your tool most likely still queries port 43, and Identity Digital no longer runs a port 43 WHOIS service for .info. An empty reply or a connection error from such a tool says nothing about whether the name is registered, so do not read it as a sign that the domain is free. Use a lookup that speaks RDAP, such as whois.com.tr, to see the actual registry record.
How do I find when a .info domain was registered and when it expires?
Both dates sit in the RDAP record as separate events. The registration event holds the creation date and expiration holds the end of the current term, while last changed records the most recent edit. The whois.com.tr result screen places these events in the usual date fields and works out the age of the domain and the time left before it expires.
Can I find out who owns a .info domain?
The registry record will not tell you, because Identity Digital publishes no registrant name, address or email for .info names. The only role in the RDAP reply is the registrar, and that is where to turn. The registrar holds the holder's contact details and decides on requests for them under its own rules and data protection law, so explain your reason when you write to it.
What does the transfer event in a .info RDAP record mean?
The transfer event gives the date on which the domain last moved to a new registrar. Read next to the registration date, it shows how long the name has been with its current registrar. Before you buy a .info name from its present holder, look at this date together with the rest of the record's history.
How can I check if a .info domain name is available?
Search for the name on whois.com.tr, which sends the query directly to the .info RDAP service. A name with no registration record appears on the result screen as available, and you can register it through any registrar that sells .info. A taken name comes back with a registration date, an expiry date and a registrar, so the difference is easy to spot.
How can I tell if a .info domain uses DNSSEC?
You can tell from the DNSSEC status of the domain itself, which the whois.com.tr result screen shows separately from the zone. The .info zone is signed, yet an individual domain is signed only once its own DS record has been published through the registrar. An unsigned domain still resolves normally and simply lacks the extra validation that DNSSEC provides.