.aero – Openprovider

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

Registration

Successful domain registration requires:

Registered through RCP or API
AERO ID and password (needs to be filled in the "additional Data" field)
two or more nameservers
registrant e-mail address verification applies*

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.

* ICANN contact verification email is sent from an alternative email address: do-not-reply@domain-robot.org
This verification is not processed by Openprovider, but its' partner. Therefore the verification status in Openprovider panel does not apply.

Transfer

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.

Update

Owner change (trade)

Trade is possible via a regular handle update.
registrant e-mail address verification applies*

NB: the new owner also requires valid AERO credentials within the new contact handle.

* ICANN contactverification email is sent from an alternative emailaddress: do-not-reply@domain-robot.org
This verification is not processed by Openprovider, but its' partner. Therefore the verification status in Openprovider panel does not apply.

Other update

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

Deletion / Restore

Delete

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

Detailed extension information

Registry	Registry: .AERO Registry whois: whois.aero Registry web based whois: https://www.information.aero/ Registry zonefile updates: Real-Time
Domain lifecycle	domain lifecycle
Technical information	DNSSEC support: no Minimum length: 3 characters Maximum length: 63 characters Allowed characters: a-z 0-9 - IDN characters: n/a Registration period: 1-10 years Renewal date offset: 35 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: 28 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: 0 days During this period, an expired or deleted domain name can be reactivated at an additional fee.
Restrictions	Local presence required? no Does Openprovider provide local presence services? no Local activity required? no Correct nameserver configuration required? no Proof of a relationship to the aviation industry must be provided in the form of a .aero ID which can be applied for on http://www.information.aero.
Policies	https://www.information.aero/registration/policies
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: General registration agreement

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.