.app WHOIS Lookup
.app is a generic extension operated by Charleston Road Registry. Look up a .app address and see what the record contains.
- 1.494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address 216.73.216.31
.app WHOIS Lookup: Records in an Application Extension
.app is a generic extension that entered the root zone on 25 June 2015, operated by Charleston Road Registry. Its IANA record lists no WHOIS server, and in our measurement on 12 August 2026 no registration data came back on port 43. The address for registration data is the RDAP endpoint on the registry's own public API; queries are answered there, and the zone holds a DS record in the root.
The RDAP reply does carry a registrant role here, but the fields inside it are not filled with real values. In the record we measured the name field held a privacy placeholder, and the street, city, postal code, phone and email lines were closed in the same way. The only identity line left open was the organisation. The existence of the role is stated; who fills it is not.
One more detail stands out: RDAP writes status codes with the words separated rather than run together as WHOIS does. The same lock therefore appears in two different spellings across the two channels — worth knowing for an eye trained on the codes. For the same registry's other extension see the .dev WHOIS lookup, and for another extension whose port 43 has closed, the .info WHOIS lookup page.
About the .app extension
- Extension
- .app
- WHOIS server
- This extension has no WHOIS service on port 43; registration data is published over RDAP.
- RDAP endpoint
- https://pubapi.registry.google/rdap
- Registry
- Charleston Road Registry Inc.
- Delegated
- 25 June 2015
- Port 43 status
- No WHOIS server in the IANA record; no registration data arrives on port 43
- Source of record data
- The RDAP endpoint on the registry's public API
- Identity
- The registrant role is listed; name and contact lines are closed with a placeholder
WHOIS FAQ
What is the text in the holder field of a .app record?
It is not a name but the placeholder of a field closed on privacy grounds. In the record we measured, the name, street, city, postal code, phone and email lines all arrived that way, and only the organisation was open. Tools that take the placeholder for an identity value report the domain's owner wrongly. Where the real information is needed, the route is the channel of the registrar that sold the name.
Why is a .app lookup not answered on port 43?
Because the extension's IANA record defines no WHOIS server, and in our measurement no registration data came back on port 43. Since 28 January 2025 RDAP has been the definitive source of registration data for generic extensions, and the obligation to provide WHOIS has ended. This extension is among the clearest examples of that arrangement: RDAP is the only channel, and an older WHOIS client comes back empty here.
Why are status codes written differently in .app records?
RDAP writes the codes with the words separated instead of run together as WHOIS does, so the same lock appears in two spellings across the channels. The meaning does not change — the code still comes from ICANN's shared vocabulary and names the operation being blocked. In the record we measured, the delete, transfer and update locks had been set by the registrar. Our result screen prints an explanation beside each code.
Does a .app record show creation and expiry dates?
It does. The RDAP reply gives dates as event records: registration, expiry and last change are listed separately. Our result screen places them into the date fields and works out the domain's age and remaining term. So the closure of port 43 costs you no date information — only the channel the data travels on has changed.
How is DNSSEC status read for a .app address?
At the level of the extension, the .app zone holds a DS record in the root, which we verified during the measurement. For an individual address the secure DNS section of the RDAP reply is what to read; it reports whether signing has been published for that name. We show the two facts separately on the result screen, because a signed zone does not make an address signed.
How does an available .app name appear in a lookup?
Query a name nobody holds and the RDAP endpoint reports that no record exists, with no fields at all. That means the name looks free to register. We keep such a result for five minutes only and registered ones for six hours, the short window being there because a name that looks free can be taken quickly.