Documented launch phases and registry events across domain extensions. Published records preserve their original event type and date precision.
| extension | Event | Start | End | Source |
|---|---|---|---|---|
| .vivo | IANA registration Separate from delegation and commercial launch | May 26, 2016 | Not specified | View source Observed Oct 14, 2026 |
| .autos | limited_registration | May 26, 2016 | Jul 3, 2016 | View source Observed Oct 14, 2026 |
| .datsun | Trademark claims | May 26, 2016 | Aug 24, 2016 | View source Observed Oct 14, 2026 |
| .infiniti | Trademark claims | May 26, 2016 | Aug 24, 2016 | View source Observed Oct 14, 2026 |
| .jcb | Trademark claims | May 26, 2016 | Aug 24, 2016 | View source Observed Oct 14, 2026 |
| .nissan | Trademark claims | May 26, 2016 | Aug 24, 2016 | View source Observed Oct 14, 2026 |
| .games | IANA registration Separate from delegation and commercial launch | May 24, 2016 | Not specified | View source Observed Oct 14, 2026 |
| .ipiranga | Trademark claims | May 24, 2016 | Aug 22, 2016 | View source Observed Oct 14, 2026 |
| .рус | Trademark claims | May 24, 2016 | Not specified | View source Observed Oct 14, 2026 |
| .promo | Trademark claims | May 23, 2016 | Oct 9, 2016 | View source Observed Oct 14, 2026 |
This history is incomplete. Past submitted launch periods do not establish current enrollment, and future availability dates are only shown when an acquired source explicitly provides them.
The current result includes IANA registration for .vivo starting May 26, 2016; limited registration for .autos starting May 26, 2016; trademark claims for .datsun starting May 26, 2016; trademark claims for .infiniti starting May 26, 2016. Additional matching records may appear on later pages.
Each record retains its published event type and date precision. A calendar date without an original time zone does not provide an exact worldwide start time.
No. A past event records a period in the extension’s history. Its source may describe the phase, but current registration eligibility must be checked against current registry policy.