List of services and tools
Services and tools | Test version |
---|---|
Registrar web Log-in service where registrars maintain their own data. The primary contact for each registrar is assigned an administrator account and can create additional users. All users with admin rights must be personal and the user must complete the registrar test before the user is created. | Registrar web test |
Registrar web API The registrar web offers an API which should be used for downloading portfolio lists. Before you use the API you must create an API user. The API requires authentication with this username and password, and then supplies a token for further use. | Registrarweb-API test |
EPP client Tool used to register and update domain name and holder information. Available via web browser. | EPP client test |
EPP server Protocol for the transfer of data between machines in connection with the registration and maintenance of domain names. Primary interface with the registration system. | EPP server test |
Applicant's declaration tool Tool where domain name holders accept subscription terms and conditions by signing a personal declaration. Available via web browser. | Applicant's declaration tool test |
Personal ID Service for private individuals registering a domain name. Creates a unique ID to use instead of the person’s national identity number. Available via web browser. | Personal ID test List of test persones |
Registrar whois Closed whois service for registrars only. Available via web browser and command line. | Registrar whois test |
Whois (no web-proxy) Open service where anyone can look up and find registered information about a domain name. Available via command line. The service is being phased out. | Whois test (no web-proxy) |
DAS Open service where anyone can look up a domain name to see if it can be registered. Available via web browser and command line at port 43. | DAS test (no web proxy) |
RDAP Protocol that will replace the current whois protocol. Under development. Available via web browser and command line. | RDAP test |
DNS check Tool where registrars and others can test whether there is a problem with the setup against some of the name servers. |
Password requirements
Accepted characters
A-Z
a-z
0-9
space
– ! # $ % & * + , . \ / : ; < = > ? @ _ " ~ ( ) { } [ ]
EPP password
The EPP password can be changed via the EPP channel or via the registrar web.
The password protects the registrar’s EPP account and must be used to access the EPP channel. The password may only be changed by the registrar owning the account.
The password must have no less than 8 and no more than 16 characters.
Accepted characters are listed above. In addition, passwords cannot be too simple; they must meet certain criteria for password strength. Shorter passwords must be more complicated than longer passwords to be considered to have the same strength. If the attempt to change the password is rejected, the solution may be to try a longer or more complicated password.
Tip: It is recommended to use at least 12 characters in practice. This increases the likelihood that the password will meet all the requirements.
Example: my$eCret-8fs contains 12 characters and satisfies the requirements.
User password on the registrar web
User passwords are set via the registrar web.
The password protects users, who can log on to the registrar’s account on the registrar web. The password can only be changed by the user themselves or by one of the registrar’s admin users.
The password must have no less than 8 and no more than 64 characters.
Otherwise, the requirements are the same as those for EPP passwords.
Tip: It is recommended to use at least 20 characters in practice. This increases the likelihood that the password will meet all the requirements.
Example: myUser$ecret8fs123() contains 20 characters and satisfies the requirements.
Transfer code (AuthInfo)
The code must have no less than 8 and no more than 64 characters. Accepted characters are listed above. The characters must be chosen from at least two of the four groups.
Example: my$ecret8fs123