Glossary of Terms¶
- Acquirer¶
a person or an organization that acquires the system
- AKM¶
automated keyset management, see also the AKM concept
- CLI¶
command-line interface
- Customer¶
a registrar or registrant or end user
- CZ-specific¶
This feature, setting or component is specific to the CZ.NIC and may require customization before it can be used in another environment.
- db¶
database
- Designated registrar¶
The registrar who is in management of a registrable object, also called the sponsoring registrar.
- DNSSEC¶
DNS Security Extensions, a suite of specifications for securing certain kinds of information provided by the Domain Name System (DNS) as used on Internet Protocol (IP) networks. See also RFC 4033, RFC 4034, RFC 4035.
- Domain owner¶
See Registrant.
- Drop catching¶
The process of acquiring a domain name immediately after it has been deleted from the registry. This is often done by automated systems to target and register domains the moment they become available.
- ENUM¶
electronic mapping of telephone numbers, see also About ENUM (CZ.NIC) or ENUM (ICANNWiki)
- EPP¶
extensible provisioning protocol, see also the EPP Reference Manual or RFC 5730
- Feature¶
a user-visible aspect, quality or characteristic of software
- FQDN¶
Fully Qualified Domain Name (an absolute domain name) contains labels of all nodes up to a TLD and the root domain.
- GDPR¶
General Data Protection Regulation. Wikipedia, Regulation (EU) 2016/679 (official source)
- Gloss¶
Simple logging backend.
- Holder¶
See Registrant.
- KEYSET¶
Key set, a shared object that contains a list of DNSSEC keys and is referenced by domains.
- Label¶
A name of a node in the DNS.
- NSSET¶
Nameserver set, a shared object that contains a list of nameservers and is referenced by domains.
- Object owner¶
A contact which is authorized to request changes of a registrable object. These are the technical contacts in nssets and keysets, the contact itself, or the domain owner.
- PAIN¶
PAyments and INvoices. See The Future of Payments & Invoices.
- Public request¶
This is a request that is submitted directly to the Registry through its public website, see Public requests.
- RDE¶
Registry Data Escrow (RDE) is the process by which a registry periodically submits data deposits to a third party called an escrow agent. These deposits comprise the minimum data needed by a third party to resume operations if the registry cannot function and is unable or unwilling to facilitate an orderly transfer of service. See RFC 8909
- Registrable object¶
A data object stored in the Registry that can be registered and modified by registrars. There are four types: domains, contacts, nssets, and keysets.
They are also called managed objects in the EPP.
- Registrant¶
Registrant is the contact which is assigned as the domain owner; also called the holder.
- ROID¶
Repository object identifier, generated by the Registry during creation of a registrable object.
This identifier should uniquely identify the object world-wide. It is composed of two parts separated with a hyphen, e.g.
D0010123116-CZ. The first part is unique within the Registry and is defined by the Registry. The second part (Repository id suffix) must be unique world-wide and it is assigned to the Registry by IANA organization.- Sponsoring registrar¶
See designated registrar.
- VAT¶
value-added tax