Documented launch phases and registry events across domain extensions. Published records preserve their original event type and date precision.
| extension | Event | Start | End | Source |
|---|---|---|---|---|
| .佛山 | IANA registration Separate from delegation and commercial launch | Jul 17, 2014 | Not specified | View source Observed Oct 14, 2026 |
| .娱乐 | IANA registration Separate from delegation and commercial launch | Jul 17, 2014 | Not specified | View source Observed Oct 14, 2026 |
| .saarland | limited_registration | Jul 17, 2014 | Aug 16, 2014 | View source Observed Oct 14, 2026 |
| .saarland | qualified_launch | Jul 17, 2014 | Sep 15, 2014 | View source Observed Oct 14, 2026 |
| .soy | qualified_launch | Jul 17, 2014 | Sep 24, 2014 | View source Observed Oct 14, 2026 |
| .saarland | Sunrise | Jul 17, 2014 | Sep 15, 2014 | View source Observed Oct 14, 2026 |
| .scot | Landrush | Jul 15, 2014 | Sep 16, 2014 | View source Observed Oct 14, 2026 |
| .moscow | limited_registration | Jul 15, 2014 | Aug 13, 2014 | View source Observed Oct 14, 2026 |
| .scot | limited_registration | Jul 15, 2014 | Sep 16, 2014 | View source Observed Oct 14, 2026 |
| .москва | limited_registration | Jul 15, 2014 | Aug 13, 2014 | 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 .佛山 starting July 17, 2014; IANA registration for .娱乐 starting July 17, 2014; limited registration for .saarland starting July 17, 2014; qualified launch for .saarland starting July 17, 2014. 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.