Requirements and Properties of the .at TLD
Technical and contractual requirements for the .at TLD
The .at is a ccTLD. This article documents all technical, operational, and contractual requirements for this TLD as well as special considerations when dealing with registry, registrar, and domain management.
General Information
TLD Type:
ccTLD
Domain Lifecycle
Registration Period:
1 JahrRenewal Period:
1 JahrGrace Periods:
- Add Grace Period: 0 days
- Standard Grace Period: 0 days
- Redemption Period: 60 days
- Pending Restore: 7 days
- Pending Delete: 59 days
Deletion Policies:
Immediate, On expirationAuto-Renew Enabled:
YesAuto-Renewal Before Expiry:
7 days before expiration
Launch Phases & Availability
General Availability:
2025-01-01T00:00:00ZTMCH/Trademark Claims:
Yes
Domain Characteristics
Domain Length:
1 to 63 charactersIDN Support:
YesPremium Domains:
YesReserved Domains:
YesRegistry Lock:
Yes
Contacts & Roles
Required Contacts:
Domain Owner, Technical ContactSupported Roles:
Domain Owner, Technical Contact, Billing ContactPrivacy Proxy Allowed:
YesContacts Transferable:
YesAllowed Postal Types:
InternationalAuthInfo Required:
Yes, Length: 6 to 16 characters
Nameservers & DNS
Nameserver Count:
2 to 8Host Objects Allowed:
YesDNSSEC Allowed:
YesDNSSEC Required:
YesDNSSEC Mode:
DSUpdate Interval:
CZDS (Zone Download):
Yes
Transfer Policy
Transfer Lock Enabled:
YesLock Duration:
Transfer Duration:
0 daysTransfer Extends Domain:
Yes, Time: 1 yearTransfer via AuthInfo:
YesConfirmation Required:
Both parties
WHOIS & RDAP
WHOIS Server:
whois.nic.atRDAP Server:
None
Dispute Resolution
Dispute Resolution Available:
YesProcedure:
Domain DisputeReference:
https://www.nic.at/en/how-at-works/faqs/domain-disputes-and-wait-statusUDRP Support:
YesURS Support:
Yes
Local Presence Requirements
Local Presence Required:
YesApplicable Contact Types:
Domain Owner, Administrator, Technical Contact, Billing ContactRequirements:
Physical Address, Business EntityEligible Countries:
Implementation Notes
- Ensure complete TLS/SSL configuration in all environments
- DNSSEC should be actively used when supported
- AuthInfo must meet minimum requirements (e.g., 12 characters)
- Note different status codes or dispute policies for ccTLDs
- Check if third-level structures (co.uk etc.) need separate documentation