Domain Name Record - The information stored in the Registry about a specific Domain Name, namely its Registrant, Managing Registrar, Administrative Contact, Technical Contact, Zone Contact and DNS Name Servers. See scheme in API basics.
Expiry Date - The date on which a Domain Name Record is scheduled to expire. Domain Names can be registered, renewed or reassigned in whole Registration Units only, and in every occasion, expiry may not exceed the Maximal Registration Period from the date of the transaction.
Handle - A Contact Object's (as defined in API Basics - Object) unique identifier within the Registry. A Handle is created automatically by the API Server upon the creation of a Contact Object, and is of the following format:
<AR Code>-<xy><number>-IL where:
<xy> – Name initials of the Contact.
<number> – An integer.
The hyphens and the string IL are constants.
IL Extensions - The Registry's additions to the Standard EPP. The IL Extensions implementation is guided by RFC 3730.
ISOC-IL - The Israel Internet Association. Administrator and operator of the .il ccTLD Registry.
IRI - The Information Retrieval Interface provided by the Registry to the AR. The IRI is described in detail in the IRI Documentation Page.
Managing AR - The AR responsible for a particular Object.
In a Domain Name Record, AR's name is an Attribute of the Object.
In a Contact Object, AR Code forms a part of the Object's Handle. Maximal Registration Period
Maximal Registration Period - Five Registration Units.
Request - HTTPS request with Client-authenticated TLS. The body contains the appropriate XML for the desired Registration Action sent by the API Client to the API Server.
Role - A Domain Name Record contains three Contact Objects (see scheme in API basics). Each Contact Object has a title, namely: Administrative Contact, Technical Contact and Zone Contact, collectively referred to as Roles.
The differences between the different Contacts authorities are outside the scope of this document.
Standard EPP - Extensible Provisioning Protocol, published in RFC 3730.