nicsk

.sk registrar module

The registry for .sk, the Slovak country-code extension, is SK-NIC, where registrars manage domains over the EPP protocol. The nicsk module builds this connection into WHMCS: .sk and .org.sk domains are ordered, renewed, transferred and managed day to day just like any other domain in WHMCS, and the module sends the necessary EPP commands in the background.

Customers set the nameservers, contact details, registrar lock and DNSSEC in the usual client area, and administrators see the actual state of the domains through WHMCS synchronisation. The module is for providers using WHMCS who manage .sk domains directly, with their own SK-NIC registrar account.

How it works

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

Registrant details. SK-NIC requires a legal form for the registrant: for a company or sole trader, a company identifier (IČO, company registration number or EU VAT number); for a private individual, the full date of birth. The module collects these in additional domain fields, and sends names and addresses with the correct accents. The legal form and the identifier can’t be changed later; that requires a new contact and a change of registrant.

Transfer. A transfer starts with an EPP code; SK-NIC approves it automatically, and the domain usually moves within a minute, which WHMCS transfer synchronisation then completes. The transfer extends the domain by one year and is billed as a renewal. After that, the module replaces the contacts with the customer’s details and turns on the registrar lock, as it does after every new registration.

Renewal and redemption period. A deleted domain stays in a redemption period for a while, during which it can still be restored. If a renewal arrives at that point, the module first restores the domain and then renews it; synchronisation reports a domain in the redemption period as expired.

DNSSEC. DS records can be added and removed on a separate page of the client area; the module validates the algorithm (8, 10, 13, 14, 15, 16) and the digest type (SHA-256, SHA-384).

Certificate-based connection. SK-NIC requires a TLS client certificate for the EPP connection, which has to be registered in the registrar console; a self-signed certificate is fine, and the module provides its own script to create one. The module verifies the SK-NIC server certificate on every connection and uses at least TLS 1.2. Every EPP command is recorded in the WHMCS module log, with the password, the EPP codes and dates of birth masked. The SK-NIC test environment (OT&E) can also be selected in the settings.

Main features

  • Registration for 1–10 years, transfer and renewal, and restore from the redemption period when needed.
  • Nameserver management, with automatic creation of missing nameserver objects; private nameservers under the domain.
  • Registrar lock, turned on automatically after registration and transfer.
  • Editing contact details; if a contact wasn’t created by the module or belongs to another customer, the customer gets a new contact of their own instead.
  • A new EPP code on every request.
  • Deletion, synchronisation (status, expiry, domain transferred away), transfer synchronisation.
  • Availability checks; blocked 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, and the details go into the log.

Limitations

  • The SK-NIC EPP interface provides no pricing information, so prices have to be set manually in WHMCS (the transfer price is a one-year renewal).
  • The module doesn’t read the EPP message queue; it always takes the status from querying the domain.
  • It doesn’t create auxiliary (aux) contacts and doesn’t use a billing contact.
  • The registrant’s legal form and identifier can’t be changed on an existing contact.