Cloud Registry Management Platform » Features

Unlike traditional registry platforms, which tend to retrofit new TLDs into the registration model of the original TLD for which they were written, CRMP was developed from the ground up to be free from legacy restrictions.

Thick Registry Model

The baseline implementation for CRMP is that of a modern thick ICANN gTLD registry model. Recognizing that each registry has its unique namespace model and registration policies, CRMP offers many configurable options with sensible defaults and allows for further customizations through our revolutionary plug-in mechanism.


CRMP is a true multi-tier system that includes an advanced front end EPP server implementation that conforms to RFC 5730, 5731, 5732, 5733, 5734 and 5910. It is designed to withstand high transaction volumes, with the ability to perform code upgrades on the fly without severing registrar connections.

The EPP server implementation is compatible with existing gTLD registries, and uses SSLv3/TLSv1 with client authentication. It also has the ability to limit the number of connections per registrar, regardless of how many IP addresses or subnets they use.


Advanced Internationalized Domain Name support is built right into the core of CRMP, not bolted on as an afterthought. It conforms to ICANN’s Guidelines for Implementation of IDNs version 2.2 and adopts proven industry practices recommended by various language and technical communities. It supports a conservative, per-script or per-language table-based approach. All language tables and associated rules that are published on the IANA IDN Language Repository are supported natively and may be turned on individually.

CRMP also supports complex bundling and blocking policies as required by some languages.


Support for the IDNA2008 standards will also be available when it is finalized by the IETF IDNAbis working group. IDNA2008 updates the original IDNA protocol to remove the Unicode version 3.2 limitation, and fix issues discovered from implementation experience.

DNS Publishing

CRMP publishes zone updates in near real-time (or at a predefined interval, if so desired) to a hidden master DNS server, from which point they are replicated to all slaves around the DNS anycast network cloud. In our hosted offering, we work with a top-tier DNS provider who provides anycast-enabled network with world-class connectivity and DDoS protection.


With mounting DNS security concerns and the imminent signing of the root zone, DNSSEC is expected in the launch strategy of every new TLD. CRMP offers full DNSSEC capabilities allowing it to publish and fully manage a signed zone. This includes the ability for registrars to provision keys over EPP, as well as the management of DS keys with the root zone and updating of trust anchors at the ISC DLV registry.


Being an ever more important part of any registry offering, CRMP offers a high-performance Whois server that uses its private copy of the thick registry database in order to achieve isolation from the registrar provisioning services. The Whois output is completely customizable, and has built-in support for multiple IDN display formats.

The CRMP Whois server is completely isolated from other parts of the system, and uses a optimized, asynchronousely replicated copy of the core provisioning database.


CRMP provides support for IPv6 at two important points. Firstly, CRMP includes the ability for registrars to provision host glue records over EPP. Secondly, in our hosted offering, our DNS anycast network provider assigns multiple IPv6-capable NS records for the purpose of serving the TLD.

Web Administration Interface

CRMP includes an intuitive, comprehensive web-based administration interface for managing all aspects of the domain registry. Registrars with no EPP capability can use it to register and manage names. Registry operators can also use it to access a superset of tools available to the registrars.

Following are just some of the features included in our web administration interface:

  • Zone Policy Configuration
    • Domain lifecycle (grace periods, pendingDelete window, etc.)
    • Reserved names lists and patterns
    • Minimum registration period
    • SOA record configuration
  • Standard operations on registry objects
    • add, update, delete, renew, transfer, info, check
    • All writable transactions are recorded with an audit trail
    • Each update transaction can optionally include a note/remark which is shown on the info screen
  • Registrar and User Management
    • Create and edit registrars/users
    • Manage granular per-zone permissions
  • Real-time stream of created domains
  • Interactive Charts and Reports
  • Fully localizable with language auto-detection
  • Skinnable through the use of templates


Ticket Tracking System

Registrar support constitutes a large part of managing a TLD registry. While CRMP is excellent at automating many otherwise manual labour-intensive chores, there are always the occasional ad-hoc queries and troubleshooting requests from registrars. Having extensive experience in registry management, Cloud Registry provides a ticket tracking system customized for domain registry support functions.

Sunrise and Land Rush mode

CRMP is tailored for modern TLD launch phases, and caters for variations in sunrise and land rush policies via its flexible plug-in architecture. A unique characteristic of the sunrise phase is that multiple applications for a single domain name are possible. Applications for a domain name are submitted along with supporting information (some may be out-of-band) and are typically processed by a trademark validation agent. Cloud Registry will work with a renowned trademark validation agency to ensure streamlined processing of applications. CRMP has a mode of operation specifically tailored for this unique case.

CRMP will also cater for various land rush scenarios, with configurable policies that can be applied to the land rush phase. At the completion of the land rush period, domains with multiple applications will be handed off to an auction house for ownership resolution.

Trademark Clearinghouse and URS

The Implementation Recommendation Team (IRT) convened by ICANN has proposed several solutions to the trademark protection issues in connection with the introduction of new gTLDs. These proposals were later refined by the GNSO STI review team. While these proposed solutions are yet to be finalized, Cloud Registry expects some of them to make their way into the new gTLD final applicant guidebook. As such, we will be following the topic closely and implementing the solutions in CRMP as required.

Registry Data Escrow

All new gTLD’s are required by ICANN to work with an escrow provider to ensure continuity in the event of catastrophic failure. CRMP includes the ability to periodically dump the registry database in a format conformant to the draft ICANN gTLD escrow specifications. We also anticipate working closely with ICANN staffs on interoperability testing and refining the specifications.

Zone File Access

Under the ICANN gTLD program, registry operators are required to make available its zone file to legitimate parties. CRMP includes the ability to export the TLD zone file periodically, and make it available to authorized parties. In addition, CRMP will also provide streamlined tools for managing the requests for zone file access. In our hosted offering, a secure HTTP or FTP server will be set up for serving the zone file to authorized parties.