.at WHOIS Lookup
.at is the country-code extension of Austria, administered by nic.at. Look up a .at 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
.at WHOIS Lookup: nic.at Records and Handles
.at is Austria's country code extension, delegated into the root zone on 20 January 1988 and operated by nic.at GmbH in Vienna. Queries are answered on port 43 by whois.nic.at, and the layout departs entirely from generic practice: the field labels are lower case and carry short names such as domain, registrar and nserver. In our measurement on 12 August 2026 the reply returned seventeen distinct labels.
The holder is identified not by a name but by a handle, and technical contacts work the same way — one record can carry several technical handles. Further down the reply each handle is resolved in a block of its own: person name, organisation, street address, postal code, city, country, phone, fax and email. In the corporate record we measured every one of those lines was open, so .at is one of the extensions where contact data can still be found inside the reply.
The date side, by contrast, is thin: the reply holds neither a creation date nor an expiry date. Its only date is the changed line, written in an unusual form with the year, month and day run together. You cannot learn from this channel how old a .at address is or when it runs out. To compare neighbouring markets, the .de WHOIS lookup and .ch WHOIS lookup pages show the same measurement for those extensions.
About the .at extension
- Extension
- .at
- WHOIS server
- whois.nic.at
- RDAP endpoint
- This extension has no RDAP endpoint in the IANA bootstrap registry.
- Registry
- nic.at GmbH, Austria
- Delegated
- 20 January 1988
- Fields measured
- 17 labels (12 August 2026)
- Withheld
- Creation date, expiry date and status codes are absent from the reply
- RDAP
- IANA's bootstrap registry defines no endpoint for .at
WHOIS FAQ
Does a .at WHOIS record show the holder's name?
In the corporate record we measured it did. The holder appears first as a handle, and that handle is then resolved in a block of its own carrying person name, organisation, address, phone and email. This is one of the extensions where contact data can be read straight from the reply. Do not expect the same on every address you query: where the holder is a natural person, those lines may be closed under data protection rules.
What does the handle in a .at record mean?
A handle is the unique identifier of a person or organisation record in the nic.at database; in the record we measured both the holder and the technical contacts were shown that way. If the same party is on another .at address, the identical number appears there too. That makes the handle the most direct way to tell whether two addresses belong to one registration record — similar names on their own prove nothing.
Why is there no registration date in a .at WHOIS record?
Because nic.at does not publish that field at all; in the 12 August 2026 measurement neither a creation nor an expiry date was present. The only date in the reply is the changed line, which says when the record was last edited. A name server change or a contact update moves it forward too, so it does not tell you when the name was first taken. Domain age cannot be calculated from .at WHOIS.
Can one .at domain carry several technical contacts?
It can. The record we measured held two separate technical handles, each resolved in its own block further down the reply. This shows up where a large organisation splits technical responsibility across teams. Seeing more than one technical block in a result does not mean the record is broken: each block matches its own handle and stands for a different person or team.
Why does the date format look unusual in .at output?
nic.at writes the change timestamp with the year, month and day run together and the time appended, unlike the ISO layout and hyphen separators used by generic extensions. If you parse .at output with a tool of your own, a date parser written for .com will not read it. On our result screen the dates are converted to a common format, and the untouched reply stays available in a separate tab.
Why are there no status codes under .at?
The reply carries no EPP status codes; our measurement found no field of that kind at all. Those codes are a requirement of the ICANN contracts that bind generic extensions, while country code extensions choose their own layout. In practice this means you cannot read from WHOIS whether a .at address carries a transfer or deletion lock — that information sits with the registrar.
Can .at registration data be queried over RDAP?
No. IANA's RDAP bootstrap registry defines no endpoint for .at, which our measurement confirmed. Since 28 January 2025 RDAP has been the definitive source for generic extensions, but country code extensions fall outside that arrangement. So the port 43 WHOIS service is the only machine-readable source for .at data, and it answers in plain text.
How does an available .at name appear in a lookup?
Query a name nobody holds and the server reports that no match was found: no handle, no name server and no contact block arrives. 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.