This article describes the procedures and requirements of .aero domain names.
Click on the subject below to open the dropdown for more information.
Successfull domain registration requires:
- AERO ID and password
- two or more nameservers
NB: as per ICANN's contact verification requirements, we are obliged to send an e-mail to the domain owner if his e-mail address was not verified before. Failure to respond to this e-mail may lead to suspension of any gTLD domain name with this same e-mail address in the owner contact.
Successfull domain transfer requires:
- AERO ID and password
- Supplying two or more nameservers
NB: See transfer troubleshooting article for possible solutions of transfers problem if needed
|Authorization code required||yes|
|Method of confirmation||authcode,email|
|Registration period after transfer||extends|
|Average transfer time||6 days after confirm|
|Advanced and simple transfers available||Contact our Sales department to check if easy transfer of 100 or more .aero domains is available.|
Owner change (trade)
Trade is possible via a regular handle update.
NB: the new owner also requires valid AERO credentials within the new contact handle.
- Domain attributes update - via RCP or API, real-time
- Handles updates - via RCP or API, real-time
NB: If domain owner's email address changes, we're obliged to start a contact verification process if this new email address wasn't verified before. Failure to respond to this e-mail may lead to suspension of any gTLD domain name with this same email address in the owner contact
- Delete - via RCP or API
- Domains, deleted explicitly - locked in quarantine 30 days after deletion
Restore / reactivate
- Restore - via RCP or API
- Restoration process is manual, can take up to several business days
|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.