Insights / ccTLDs & gTLDs
What Is the Sunrise Launch Process for Domains?
Originally published on dns.africa
A Sunrise period is one of the first high-stakes operational events in a new top-level domain launch. If you are asking what is sunrise launch process, the short answer is this: it is a controlled registration phase that gives eligible trademark holders an opportunity to secure matching domain names before the extension becomes available to the public.
For registry operators, Sunrise is not simply an early-access sales window. It is a rights-protection mechanism, a policy implementation exercise, and a test of registry, registrar, validation, billing, and support operations. A well-executed Sunrise launch protects the namespace’s credibility while establishing a disciplined foundation for the stages that follow.
What Is the Sunrise Launch Process?
The Sunrise launch process is the set of policies, systems, and operational procedures used to accept and process domain name applications from verified rights holders before general availability. It is usually one of the first phases on a new gTLD launch checklist. In the new gTLD environment, eligibility commonly depends on a valid Signed Mark Data file, or SMD file, issued through the Trademark Clearinghouse. That file confirms that the underlying trademark record has been validated for use in applicable rights-protection mechanisms.
The core objective is straightforward: provide trademark owners with a defined opportunity to register domain names that correspond to their marks. The operational reality is more complex. The registry must determine eligibility rules, application timing, name matching requirements, allocation rules, pricing, dispute procedures, and registrar readiness before the first Sunrise application reaches the shared registration system.
Sunrise periods are most closely associated with new generic top-level domains, although country-code operators and private namespace managers may use comparable priority phases. The governing registry agreement, launch policy, and applicable local requirements determine the exact model. A registry should not assume that a Sunrise policy designed for one extension can be copied unchanged to another.
Why Sunrise Matters to Registry Operators
A credible Sunrise program serves both trademark owners and the long-term health of the namespace. It reduces avoidable conflict at launch, gives rights holders a predictable process, and demonstrates that the registry has taken rights protection seriously from day one.
It also creates operational discipline. A Sunrise launch forces the operator to verify that its EPP workflows, registrar interfaces, reserved-name policies, validation connections, reporting, billing controls, and customer-support escalation paths work under real launch conditions. Problems that surface during Sunrise are easier to contain than problems that appear after general availability, when registration volumes and public scrutiny can rise sharply.
There is a commercial consideration as well. Sunrise pricing is often higher than standard registration pricing because of the specialized validation and policy administration involved. That can support launch economics, but excessive pricing or unclear eligibility requirements can weaken participation and create reputational friction. The appropriate approach depends on the extension’s market position, rights-holder audience, and broader launch strategy.
The Main Stages of a Sunrise Launch
1. Define the launch policy and eligibility rules
The process begins with policy design. The registry establishes which rights holders may apply, what evidence they must provide, what labels are eligible, and how applications will be handled when multiple qualified parties seek the same domain name.
For many new gTLD launches, a valid SMD file is the principal eligibility credential. However, the registry must still define important details: whether exact-match rules apply, how spaces and punctuation are treated, whether certain categories of marks are excluded, and whether Sunrise applications can be transferred or modified during the launch phase.
The policy should also set clear treatment for reserved names, blocked names, geographic terms, premium inventory, and names subject to legal or regulatory restrictions. These decisions must align with the registry’s business plan and technical implementation. A policy that cannot be enforced consistently through the registry platform will create exceptions, manual work, and unnecessary dispute exposure.
2. Choose the Sunrise allocation model
A Sunrise phase can use different allocation approaches. In an end-date model, qualified applications are collected until the period closes, and competing applications may be resolved through auction, priority rules, or another published allocation method. In a first-come, first-served model, eligible applicants can register names as soon as the window opens, subject to the registry’s stated rules.
Each model has trade-offs. First-come, first-served is easier for registrars and applicants to understand, but it places greater emphasis on opening-time readiness and connection fairness. An end-date model can reduce the advantage of speed, yet it requires a clear and trusted process for handling contention after the application window closes.
The choice should reflect the registry’s intended market behavior, anticipated demand, and the capacity of its registrar channel. A highly anticipated extension may benefit from a controlled contention process. A specialized, lower-volume extension may prioritize simplicity and rapid registration.
3. Configure the registry platform and validation workflow
Once policy is approved, technical configuration converts it into enforceable registry behavior. The registration system must recognize the Sunrise phase, validate required credentials, apply phase-specific pricing, enforce reserved-name rules, and return accurate statuses through EPP and registrar portals.
The registry also needs reliable integration with the applicable trademark validation process. A successful credential check is not the same as a successful registration. The platform must confirm that the requested label complies with the registry’s Sunrise matching rules, that the name is available, and that the sponsoring registrar is authorized to submit the transaction.
This is where experienced registry infrastructure matters. At DNS Business, that infrastructure is rEngin, the core of the DNS Business registry system. Registry operators use rEngin Console to manage registrars, domains and registry functions, so Sunrise phases, phase-specific pricing, reserved names and launch policies are configured in the registry platform itself and applied consistently at scale, rather than through generic commerce workflows that do not understand domain lifecycle rules.
4. Prepare registrars, documentation, and support teams
Registrars are the registry’s route to market, so their readiness directly affects Sunrise performance. Before launch, registrars need access to policy documentation, technical specifications, test environments where appropriate, pricing details, timelines, and clear guidance on error codes and application statuses.
On rEngin, registrars and resellers use rEngin Portal to manage their account, onboarding and domain functions, which gives every channel partner the same view of launch phases, pricing and application statuses. rEngin Portal version 3 is the latest release, already live at ZACR, RyCE, Gateway SRS and Registry Africa, with the next deployment at ZARC; ZARC and Registry Africa are the two largest registries in the DNS Business portfolio. For more on bringing registrars on board, see Registrar Onboarding on rEngin SRS.
Support teams need equally precise preparation. They should know how to distinguish credential failures from name eligibility failures, how to explain allocation timelines, and when an issue requires escalation to policy, legal, or technical operations. Trademark holders are often represented by specialized agents, and they expect accurate answers rather than general consumer-domain support language.
Registry operators should also prepare public-facing materials that explain the process without overstating rights. A Sunrise-eligible trademark holder has the right to apply under the published rules. Eligibility does not always guarantee final allocation when multiple qualified applicants seek the same name.
5. Open, monitor, and manage applications
When Sunrise opens, the focus shifts to transaction integrity and operational visibility. The registry should monitor application volume, EPP response performance, credential-validation outcomes, failed commands, registrar activity, billing events, and any concentration of applications around high-value labels.
Real-time monitoring is particularly valuable at the opening of a first-come, first-served period. Even modest volumes can expose configuration errors, time synchronization issues, unanticipated registrar behavior, or inconsistencies between the policy and system rules. A launch command center with technical, policy, and support representation helps teams resolve issues quickly and document decisions consistently.
Transparency matters during this stage. If the registry identifies a material issue, it should communicate the impact, corrective action, and any relevant timing changes through established registrar channels. Quietly applying exceptions after the fact can undermine confidence in the launch process.
6. Resolve contention, disputes, and final allocation
After the application window closes, an end-date Sunrise moves into allocation. The registry identifies names with more than one qualified application and applies its published contention method. Depending on the launch design, this may involve an auction, priority evaluation, or another transparent selection process.
The registry must also be prepared for Sunrise challenges. A challenge mechanism allows parties to question whether a registration met the applicable eligibility requirements. The rules, fees, timelines, evidentiary standards, and independent review process should be established before launch, not improvised after a complaint arrives.
This stage requires careful recordkeeping. Application data, validation outcomes, registrar submissions, allocation results, and dispute decisions should be retained according to policy and compliance requirements. Strong audit trails protect both the registry and legitimate registrants when decisions are reviewed.
Common Launch Risks and How to Reduce Them
The most damaging Sunrise problems usually arise from a mismatch between policy, technology, and communication. An eligibility rule may be legally sound but impossible to validate automatically. A registrar may understand the commercial timeline but not the EPP implementation. A contention process may be fair in principle but insufficiently explained to applicants.
Operators reduce these risks by treating Sunrise as a formal launch program rather than a configuration task. Policy review, integration testing, registrar onboarding, support training, incident management, and reporting should have defined owners and acceptance criteria. A dry run using realistic registrar transactions can expose issues that conventional system testing misses.
It is also wise to resist unnecessary complexity. Every exception category, custom matching rule, or manual approval path increases operational cost and makes consistent enforcement harder. Differentiated policies can be valuable for a strategically positioned extension, but they should be introduced only where the market benefit justifies the added risk.
Planning Beyond Sunrise
Sunrise does not operate in isolation. It should connect cleanly to the phases that follow, such as a landrush period, premium or early-access launch, trademark claims service, and general availability. Inventory state, registration term rules, pricing, reserved-name treatment, and registrar communications must transition without ambiguity.
For many new gTLDs, Sunrise is also followed by a Trademark Claims period, where prospective registrants receive notice when attempting to register a label matching a trademark record. The exact sequence and obligations depend on the applicable program rules, so registry operators should confirm current requirements early in the launch plan.
The strongest Sunrise programs make rights protection predictable without turning launch operations into a manual exception process. When policy, registry infrastructure, and registrar execution are aligned before opening day, the namespace can move into general availability with greater confidence and far fewer avoidable disputes. For the wider launch picture, see our guide on how to launch a new gTLD successfully.
Run your Sunrise on rEngin
rEngin Console and rEngin Portal give registry operators and registrars one platform for launch policy, validation and registrar readiness. Book a rEngin demo.