This article describes the procedures and requirements of .at domain names.
Click on the subject below to open the dropdown for more information.

Successful domain registration via RCP or API requires:

  • the domain's contact handles
    - Contact full name is mandatory (only 1 letter as firstname will not be accepted)
  • two or more nameservers or a nameserver group

Successful domain transfer via RCP or API requires:

  • authorisation code
  • the domain's contact handles
    - Registrant's full name is mandatory (only 1 letter as firstname will not be accepted)
  • two or more nameservers or a nameserver group
  • email sent by the .at Registry to the owner has to be confirmed in order to finish the transfer.

Additional notes on a .at transfer

  • The authorisation code is valid for 21 days.
  • After the transfer has finished, the domain owner will receive another e-mail (confirmation) from the registry.
  • Using an invalid authorisation code will present the error:
    "No open confirmation-process of the domain [domainname.at] to the registrar [648] found."
    Please reset the code at your current provider.
  • In case the current provider cannot or does not provide the authorization code, please contact us. We might be able to request the code through the registry directly. A fee of € 25,- will be charged. Please check the e-mail address of the domain holder in the whois is correct before contacting us, as the registry will send the code to that address.
Authorization code required yes
Method of confirmation authcode,email
Registration period after transfer unchanged
Average transfer time Instantly
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .at domains is available.

Owner change (trade)

  • requested as a normal domain update via RCP or API
  • processed realtime
  • both previous and new registrant will receive an e-mail. This is a notification only, no action is required.

Other update

  • requested via RCP or API
  • processed realtime


There are two ways of removing a .at domain from Openprovider:

  • Explicitly delete
    It requires written confirmation from the domain owner. The deletion form can easily be created at the registry's website and is for your own administration only.
    A delete should be done at most 24 days before the domain's renewal date.
  • "Withdrawing"
    Gives the domain back to the registry. The contractual relationship is now between registry (NIC AT) and domain owner. NIC AT will send a renewal invoice to the domain owner. If the end user wants to delete the domain, he should send a signed form to NIC AT.
    Once the domain has been given back to the Registry, Openprovider no longer manages the domain and can not assist in deleting the domain after this point. This must be done by the registrant via the form, sent directly to the registry.

Restore / reactivate

  • restore / reactivation supported via RCP or API only in case of explicit delete.
  • quarantine periods can be found under 
    Detailed extension information > Technical information > Quarantine period



Technical information
  • Available second level domains: .co.at, .or.at
  • DNSSEC support: yes
  • Minimum length: 1 characters
  • Maximum length: 63 characters
  • Allowed characters: a-z 0-9 -
  • IDN characters: yes
  • Registration period: 1 year
  • Renewal date offset: 2 days
    The number of days before the registry's expiration date, that Openprovider requires the domain to be renewed or expired. More info.
    Note that the dates as shown in your Openprovider account are always leading, even if they do not match the renewal date offset mentioned here.
  • Soft quarantine period: n/a days
    During this period, following after an expiration, the domain can be restored for free. This period does not apply if the domain is deleted explicitly. More info.
  • Quarantine period: 55 days
    During this period, an expired or deleted domain name can be reactivated at an additional fee.
  • Local presence required? no
  • Does Openprovider provide local presence services? n/a
  • Local activity required? no
  • Correct nameserver configuration required? no
  • The Domain(s) can be registered without further limitations.
  • Full name of registrant is required
  • Nameservers must be configured and return an authoritative answer before the domain is requested.
  • Terms and conditions: http://www.nic.at/en/service/legal_information/terms_conditions/
  • Registration guidelines: http://www.nic.at/en/service/legal_information/registration_guidelines/
Registration agreement The registry requires that a registration agreement is in place between the provider and the domain holder. The text of this registration agreement and any required supplements is the following:

Due to the regular changes in registry rules and configuration or missing information from registry side, and despite our effort to keep our knowledge base up-to-date, information in the knowledge base may be outdated or incorrect. If you encounter some issue, please report it through the "HotJar" feedback collector on the bottom right, or (if it is blocked by your browser) by clicking the "Submit a request" link below. No rights can be derived from the information in this knowledge base. If there is discrepancy between the knowledge base and the process in Openprovider, the process in Openprovider is leading.

Was this article helpful?
Additional questions? Submit a request