CentralNic

Registrar module

Many domain extensions run on CentralNic’s registry platform: generic TLDs (for example .xyz, .online, .site), country-code extensions (for example .fm, .gd, .vg) and second-level domains (for example .uk.com, .de.com, .us.com). The module connects WHMCS directly to CentralNic’s EPP server, so these domains are ordered, renewed, transferred and managed in the usual WHMCS workflows.

Customers set the nameservers, contacts, registrar lock and DNSSEC in the client area; administrators see the actual state of the domains through synchronisation. The module is for providers using WHMCS who work with their own CentralNic registrar account.

How it works

Live data. Every status, date, nameserver and contact arrives through an EPP call at the moment WHMCS asks for it; there is no local copy of the domains. The only table the module adds stores the contacts it has created, so that the same customer’s next registration uses them. A contact is never shared between two WHMCS clients.

Contacts. Most TLDs require a registrant, an administrative and a technical contact, but some second-level domains (for example .uk.com, .de.com) accept no contacts at all. The module registers these without contacts and shows in the client area that the registry stores no data for them. CentralNic expects contact data in ASCII, so the module transliterates accented characters (Kovács → Kovacs). Whois shows no contact data by default, and the module doesn’t change this.

Transfer. A transfer starts with an EPP code; the previous registrar can approve or reject it within five days, after which it completes automatically. The contacts don’t move with the domain: when the transfer completes, the module assigns new contacts to the domain from the customer’s WHMCS details and turns on the registrar lock. Because CentralNic never returns the existing EPP code, the module sets a new one on every request.

Renewal and redemption period. The module relies on the registrar account’s “auto-delete” renewal policy: anything that isn’t renewed before expiry is neither renewed nor billed by the registry, but placed into a 30-day redemption period. The renewal therefore has to arrive before expiry; WHMCS sends it when the renewal invoice is paid. If the payment arrives after expiry, the module first restores the domain and then renews it (the restore may carry a fee). In the WHMCS domain pricing, the grace period is 0 and the redemption period is 30 days.

DNSSEC. Every CentralNic zone is signed; DS records can be added and removed on a separate page of the client area.

Certificate-based connection. The EPP connection requires a TLS client certificate, which has to be uploaded to the registrar console; a self-signed one is accepted, and the module provides a script to create it. The module verifies the server certificate and uses at least TLS 1.2. The module log masks the password and the EPP codes.

Main features

  • Registration, transfer and renewal, and restore from the redemption period when needed.
  • Nameservers and private nameservers, with automatic creation of missing nameserver objects.
  • Registrar lock, turned on automatically after registration and transfer.
  • Management of registrant, administrative, technical and billing contact details.
  • A new EPP code on every request.
  • Deletion, synchronisation, transfer synchronisation.
  • Batched availability checks; taken, blocked and premium names are shown as unavailable.
  • DNSSEC (DS records) in the client area.
  • In the client area, only active domains that belong to the module can be modified; on a connection error, the customer sees only a generic message.

What it deliberately doesn’t support

  • Premium and Early Access names. The module doesn’t use the fee extension, so the registry rejects the registration, renewal and transfer of these names; a domain priced above the standard price can’t be bought through it.
  • Trademark claims and sunrise registration.
  • Registry Lock, CentralNic’s paid, per-domain locking service.
  • The EPP message queue: the status always comes from querying the domain.
  • Accounts with an auto-renew policy: the module only works with auto-delete.