<developers/>

Registrar modules

A registrar module says what it can do, then does it: register, transfer, renew, manage nameservers and contacts, and keep dates in step.

Last changed 12 Nov 2026

The class#

Every registrar module extends CoreInto\Registrars\Registrar. It is built with its settings (secrets opened) and acts on a DomainOrder: the domain, its term, nameservers, contacts and the client.

What it can do#

features() lists what the registrar supports, from: register, transfer, renew, nameservers, lock, contacts, epp, sync, transfer_sync, check, list, balance and child_ns. CoreInto offers only what is listed: a registrar without contacts has no contact form on the domain page, and a missing register turns registrations into staff tasks.

MethodWhat it does
title(), about(), fields()Name, set-up help and settings
presets()Extension rules the registrar knows, used to fill in Domain Pricing
test()Checks the login and returns a line about the account
check(array $names)Availability of several names
register(), transfer(), renew()The three orders
getNameservers(), setNameservers()Nameservers
getLock(), setLock()The transfer lock
getContacts(), setContacts()Registrant and other contacts
eppCode()The transfer code
sync(), transferSync()Expiry date and status, for the daily sync
listDomains(), listPage()The domains in the account, to bring them into CoreInto
balance()The account balance, shown in the settings

Throw RegistrarError with the registrar's own message when something fails; staff see it on the domain page.

Shipping a registrar as an add-on module#

Unlike gateways and server modules, a registrar can come in an add-on module: the module's registrars() method returns name => class, and its whois() and whoisTlds() can answer WHOIS for the extensions it handles. That is how the PKNIC module for .pk domains is built. See add-on modules.

Frequently asked questions

Can I sell a registrar module?

Yes. Package it as an add-on module and apply as a technology partner to be listed in the marketplace.