Launch your TLD with buyers already in line

The Frontier Registration Period is D3’s branded Limited Registration Period under the ICANN startup process. It converts demand built before launch into a points-ranked registration path before General Registration. It follows Sunrise and any agreed pre-Frontier phases, which may include private or eligibility-restricted phases and one EAP.

Yes. The registry may conduct any number of ICANN-compliant private or eligibility-restricted phases and, if it chooses, one EAP before Frontier, provided each is identified by the agreed deadline and permitted by the Participation Agreement. Qualifying Frontier orders receive the agreed reservation, hold and automatic-execution protections during those earlier phases, including execution on the earliest EAP day their Posted Price clears. Orders that do not complete earlier remain eligible for Frontier. The registry may also run later launch phases after Frontier.

The registry sets its launch pricing, premium pricing, eligibility rules, reserved names and covered inventory before the agreed inventory and pricing lock.

After the lock, the registry must honor the locked pricing and process executable orders for covered inventory. It may not use nonpublic Frontier demand to reprice, reclassify or remove a requested name.

Before the inventory and pricing lock, D3 provides only aggregate or de-identified TLD-level information that helps the registry understand where interest is developing. D3 does not disclose individual member identities, requested names or maximum prices before the registry commits its inventory and pricing.

At launch, the registry receives only the name and order information needed to confirm pricing, place required holds, issue authorization codes and complete eligible registrations.

Frontier is designed to move demand through clear stages, from broad TLD interest to indicated name demand and then to executable orders. Not all reported interest is capital backed.

Frontier separately reports TLD interest, gross indicated demand, executable orders supported by reserved or authorized purchase funds, and completed registration volume. Only executable orders should be treated as funded demand, and registration volume is reported only after registrations are completed.

Registrations are completed through participating ICANN-accredited registrars. The same technical path supports a protected Frontier order completed during an agreed private phase and orders completed during the Frontier Registration Period.

Frontier access must be available to qualified participating registrars on objective and nondiscriminatory terms. A registrar must implement the applicable Frontier API or batch process, support authorization code redemption and complete required trademark, eligibility and registrant checks.

The applicant or registry operator signs the Frontier Participation Agreement, identifies the covered TLDs and any exclusions, and discloses any agreed private pre-Frontier phases by the applicable deadline.

It incorporates the launch sequence, Frontier Registration Period and any required reservation mechanics into its ICANN startup information, then provides final inventory and pricing by the agreed lock date. It must also support the agreed order files, holds, confirmed pricing, authorization codes and settlement process.