.us WHOIS Lookup
.us is the country-code extension of the United States. Look up a .us address and see which fields the record carries.
- 1.494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address 216.73.216.31
.us WHOIS Lookup: Record Fields and the Nexus
.us is the country code extension of the United States, delegated into the root zone on 15 February 1985 and operated by Registry Services, LLC. Queries are answered on port 43 by whois.nic.us. In our measurement on 12 August 2026 the reply returned sixty field labels — among the widest records of all the extensions we measured. The zone holds a DS record in the root.
The contact side of this extension is open. In the corporate record we measured, all three blocks — registrant, admin and tech — arrived complete with name, organisation, street, city, state, postal code, country, phone and email. Where most generic extensions close those lines, a .us record stays readable; on registrations held by natural persons the same openness may not hold.
The most distinctive part of the reply is a pair of extra fields repeated in all three blocks: an application purpose and a nexus category. Together they state, in short codes, why the registration was granted and which class the holder's connection to the country falls into. No other extension we measured carries its eligibility grounds inside the WHOIS reply. For an extension on the same template see the .biz WHOIS lookup, and for a neighbour whose contact data is less open, the .ca WHOIS lookup page.
About the .us extension
- Extension
- .us
- WHOIS server
- whois.nic.us
- RDAP endpoint
- This extension has no RDAP endpoint in the IANA bootstrap registry.
- Registry
- Registry Services, LLC — United States
- Delegated
- 15 February 1985
- Fields measured
- 60 field labels (12 August 2026)
- Distinctive fields
- Application purpose and nexus category repeat in all three contact blocks
- RDAP
- IANA's bootstrap registry defines no endpoint for .us
WHOIS FAQ
Are the holder's details open in a .us WHOIS record?
In the corporate record we measured they were. The registrant block showed name, organisation, street, city, state, postal code, country, phone and email in full, and the admin and tech blocks were just as complete. Most generic extensions return those lines closed. Do not expect the same openness on registrations held by natural persons, where data protection practice can produce a different result.
What does the nexus category mean in a .us record?
It states, in a short code, which class the holder's connection to the country falls into, and in the record we measured it appeared in all three contact blocks. The extension is a zone where registration rests on such a connection, and this field preserves what that condition was at the time of registration. The full meaning of the code is defined in the registry's own rule set; the reply carries the code, not its explanation.
What is the application purpose field in a .us reply for?
It marks in a short code the purpose for which the registration was made, and sits right beside the nexus field. Together the two keep the grounds for a .us address inside the record itself. No other extension we measured publishes eligibility data of this kind in WHOIS; these fields make the basis behind an address something you can actually query.
Does a .us record show creation and expiry dates?
It does. The reply gives the creation date in Creation Date, the last modification in Updated Date and the end of the term in Registry Expiry Date, all in UTC; the record we measured was opened in 2002 with an expiry date in 2027. Our result screen derives the domain's age and remaining term from those three values and turns the indicator to a warning colour as the term runs short.
Can .us registration data be queried over RDAP?
No. IANA's RDAP bootstrap registry defines no endpoint for .us, which our measurement confirmed. Since 28 January 2025 RDAP has been the definitive source for generic extensions, but .us is a country code extension and falls outside that arrangement. However closely the reply follows the generic template, the channel behind it is the port 43 WHOIS service alone.
What do the status codes in a .us record lock?
The codes come from ICANN's shared EPP vocabulary, and the record we measured carried six of them: deletion, transfer and update were locked by both the registrar and the registry. Codes prefixed client are set by the registrar and can be lifted by it; codes prefixed server are set by the registry and the registrar cannot lift them. Our result screen prints what each code blocks.
How is DNSSEC status read for a .us address?
The DNSSEC line in the reply describes the address you queried: signed when a DS record has been published for that name, unsigned when it has not. The extension is a separate matter — the .us zone holds a DS record in the root, which we verified during the measurement. We show the two facts separately so a signed zone is never mistaken for a signed address.
How does an available .us name appear in a lookup?
Query a name nobody holds and the registry reports that no match was found, with none of the sixty fields present. 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.