Launching your dotBrand
Preparing for launch
What happens next?
Once you’ve submitted your application, completed various ICANN assessments and responded to any questions, your dotBrand registry will be evaluated to ensure it meets the technical and operational requirements before it can go live at the root of the Internet.
What is pre-delegation testing and how does it get a dotBrand delegated into the root of the Internet?
Before a dotBrand can be delegated to the root of the Internet, it needs to demonstrate that it has established the technical and operational capabilities to operate a dotBrand in a stable and secure manner. Pre-Delegation Testing, otherwise known as PDT, is conducted to ensure each critical function meets the requirements prior to being introduced to the root zone or when changes or modifications are made to the technical operations. Test elements include:
Domain Name System (DNS)
Testing operability with the Domain Name System protocols
Internationalized Domain Name (IDN)
Reviewing and/or testing domain names that include characters not written with the basic Latin alphabet (a – z)
Testing the records containing registration information about registered domain names
Testing to ensure registries can make successful data deposits with their Data Escrow agents
Testing the implementation of the protocol used for electronic communication between a registrar and a registry for provisioning domain names
Review of self-certification documents (XML) to ensure all required elements are in place
Each applicant must agree to an appointment date and will receive notification of the results upon completion. Only once your dotBrand has passed PDT can it be added to the root of the internet.
More information on PDT including self-testing tools can be found here.
Are there specific steps or processes to follow for launching a dotBrand?
As with any changes, you will need to consider how the use of your dotBrand will impact your customers, your internal functions and your business. Preparation is key; engaging and planning with internal stakeholders, co-ordinating changes with your related service provider(s), communicating with customers to educate and raise awareness of the purpose and benefits to ensure a smooth transition.
There are also steps to follow when launching any TLD, which will be detailed in ICANN’s Applicant Guidebook. After launch, it is important to maintain operations in compliance with ICANN’s Registry Agreement.
What is name collision what would I need to do about it if my dotBrand was at risk of name collisions?
According to ICANN “A name collision occurs when an attempt to resolve a name used in a private name space (e.g. under a non-delegated Top-Level Domain, or a short, unqualified name) results in a query to the public Domain NameSystem (DNS). When the administrative boundaries of private and public namespaces overlap, name resolution may yield unintended or harmful results.”
Name collisions are not new but as the New gTLD space increases, the potential for name collisions may also rise. As part of the launch process, ICANN introduced the Name Collision Occurrence Management Framework, whereby Registry Operators implement a contolled interruption perios of 90 days to alert system adminstrato
The Name Collision Occurrence Management Framework was created to mitigate the impact of name collisions in the domain name system (DNS). More detailed resources are available on ICANN’s website