Features

  • The CoCCA registry solution consists of two (2) modules: a stable and widely deployed ccTLD Shared Registry System (SRS) developed over the past 25 years, and a read-only Registry Data module that extends the Registration Data Access Protocol (RDAP).
  • The SRS and RDAP modules run on the same technical stack - Java25, PostgreSQL, Redis, Tomcat, and Nginx and comply with applicable ICANN and IETF standards.
  • the CoCCA SRS includes all the security features expected of a mature application: 2FA, IP locks, API tokens, captcha, browser fingerprinting, a one-way hash of critical data, limited validity domain authcodes, and multiple admin and registrar roles.
  • The SRS policy and commercial rules are managed via a web-based administrative portal. The SRS portal is used to add / edit registrars, configure domain lifecycle, API connections, security, string prohibitions and all other policy common to the industry.
  • Policy concerning pricing, currency, grace periods, taxes, credit card gateways, and automation is set per-registrar (not per zone), this allows TLD admins to charge fees in different currencies and accept payment via different gateways depending on the client.
  • The CoCCA SRS is compliant with ICANN's core standards for ICANN TLDs, but it allows for complex policy matrices only found in ccTLDs that must conform with local policy and the local commercial market.
  • Administrators and Registrars have access to a detailed ledger to get current and historic statistics on demand.
  • Registrars do not have to use EPP, if they wish they can provision domains and manage their domain portfolio via the SRS portal only.
  • Full IDN domain support since 2009.
  • Support for Brand Safety Alliance (BSA) and NameBlock blocking services.
  • SOA, propagation and DNS health checks via the RDAP client.
  • Premium Name support via rfc8748.
  • Bespoke National ID EPP extension.
  • Considered GDRP compliant personal data disclosure configuration tools that enable policy to based on registrar and contact location, different disclosure options for Domestic, EU, and other country locations.
  • Full IPv6 support accross all API and services.
  • Detailed auditing and retention of all registry data, even post-deletion from active tables.
  • WHMCS EPP module for frictionless registrar onboarding.
  • Eighteen payment gatways supported, many in Africa, others can be added on request.
  • Local hosting for data soverinty.

RFC Conformance

  • rfc5730 Extensible Provisioning Protocol (EPP)
  • rfc5731 Extensible Provisioning Protocol (EPP) Domain Name Mapping
  • rfc5732 Extensible Provisioning Protocol (EPP) Host Mapping
  • rfc5733 Extensible Provisioning Protocol (EPP) Contact Mapping
  • rfc5734 Extensible Provisioning Protocol (EPP) Transport over TCP
  • rfc3914 Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)
  • rfc8748 Registry Fee Extension for the Extensible Provisioning Protocol (EPP)

  • rfc10026 Operational Recommendations for DNSSEC Delegation Signer (DS) Automation
  • rfc9224 HTTP Usage in the Registration Data Access Protocol (RDAP)
  • rfc8056 Registration Data Access Protocol (RDAP) Status Mapping
  • rfc9802 Registration Data Access Protocol (RDAP) Query Format
  • rfc7481 Security Services for the Registration Data Access Protocol (RDAP)
  • rfc7484 Finding the Authoritative Registration Data (RDAP) Service

  • rfc8909 Registry Data Escrow Specification
  • rfc5890 Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework
  • rfc5891 Internationalized Domain Names in Applications (IDNA): Protocol
  • rfc5892 The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)
  • rfc5893 Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)
  • rfc4033 DNS Security Introduction and Requirements
  • rfc4034 Resource Records for the DNS Security Extensions
  • rfc5910 Domain Name System (DNS) Security Extensions Mapping
  • rfc4035 Protocol Modifications for the DNS Security Extensions
  • rfc4509 Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)
  • rfc3912 WHOIS Protocol Specification
Other, non-rfc.
  • ICANN MoSAPI Monitoring System API Specification
  • Finance EPP Balance, Price Checks
  • DS and NS automation settings / EPP Extension (draft).