Frequently Asked Questions

This page explains some important points of the Guidelines.
If you do not find the answers to your questions, please send an email to hostmaster@sk-nic.sk.

Who can become a Registrant?

Pursuant to Section 2.1 of the Rules: A Registrant may be a natural or legal person who has an address for service delivery in one of the Member States of the European Union, in the State of the European Economic Area or in a Member State of the European Free Trade Association.

This means that anyone, and hence the future .sk domain owner, can come from any country but must have a delivery address in one of the states under this condition.

The user may not have this address listed in his or her data at the time of registration (although this is definitely recommended for the removal of any other issues) but must demonstrate this fact after being invited to comply with Section 2.1 of the Rules.

The list of all states that meet this condition is listed in the following table.

 

Kód Názov [SK] Názov [EN] EU / EHS / EEA
AT Rakúsko Austria EU, EEA
BE Belgicko Belgium EU, EHS, EEA
BG Bulharsko Bulgaria EU, EEA
BE Belgicko Belgium EU, EHS, EEA
HR Chorvátsko Croatia EU, EEA
CY Cyprus Cyprus EU, EEA
CZ Česká republika Czech Republic EU, EEA
DK Dánsko Denmark EU, EHS, EEA
EE Estónsko Estonia EU, EEA
EU Inštitúcie Európskej únie European Union Institutions EEA
FI Fínsko Finland EU, EEA
FR Francúzsko/td> France EU, EHS, EEA
DE Nemecko Germany EU, EHS, EEA
GR Grécko Greece EU, EHS, EEA
HU Maďarsko Hungary EU, EEA
IS Island Iceland EEA
IE Írsko Ireland EU, EHS, EEA
IT Taliansko Italy EU, EHS, EEA
LV Lotyšsko Latvia EU, EEA
LI Lichtenštanjsko Liechtenstein EEA
LT Litva Lithuania EU, EEA
LU Luxembursko Luxembourg EU, EHS, EEA
MT Malta Malta EU, EEA
NL Holandsko Netherlands EU, EHS, EEA
NO Nórsko Norway EEA
PL Poľsko Poland EU, EEA
PT Portugalsko Portugal EU, EHS, EEA
RO Rumunsko Romania EU, EEA
SK Slovenská republika Slovakia EU, EEA
SI Slovinsko Slovenia EU, EEA
ES Španielsko Spain EU, EHS, EEA
SE Švédsko Sweden EU, EEA
CH Švajčiarsko Switzerland EEA
GB Veľká Británia United Kingdom EU, EHS, EEA

EU – European Union
EHS – European Economic Community
EEA – European Economic Area

Who will manage the User contact information under the new rules?

Each user will manage and update their contact information in the new system. Authorized contact information registrar, i.e. The registrar you choose for that task.

Since the current system does not recognize such a registrar’s role, the current user will be the Authorized Contact Information Registrar designated automated by the following key:

  1. If the user has just one authorized registrar (hereinafter referred to as “OPR”), the system designates him as an Aut. The contact information registrar of this.
  2. If a user has more than one OPR, the system will choose the one with the most domains.
  3. If the user has more than one OPR in step 2, the system selects the first in alphabetical order.
  4. OPR, which did not request to move to the new system, is not the standard reason for the algorithm, i. Is selected from other OPRs.
  5. If it is not possible to select either OPR (none requested or user does not have OPR), the system specifies the registrar according to steps 2 and 3 even if OPR is not. If this is not possible, select Auto. The contact data registrar will be in step 6. However, the user has the option to use the F7 form and modify his data until migration. To add to the OPR someone who has requested the transfer. Their current list can be found at a separate web site.
  6. If no registrar can be selected and the user has not filled in (see step 5), Aut. The contact information registrar of this user will become SK-NIC upon migration. Beware, it will be necessary to enter into a new lease agreement with SK-NIC within the next 14 days or change the Aut. The contact information registrar on another.

How do I generate my own AuthInfo code and what is this code for?

An authInfo domain code is a security element of the domain. The AuthInfo code is only visible to the current domain registrar, and it is provided to the holder. An authInfo code is necessary in order to change the domain registrar. When registering each domain, the registrar can determine whether the AuthInfo code for the domain will be automatically generated or manually enter it. The code can be used by a domain owner or New registrar, it is important to ensure that this code is maintained using the highest possible level of security.
The AuthInfo code is not limited by the number of characters, but SK-NIC recommends that you use at least 12 characters, and the code should have both lower and upper case letters, digits and a special characters similar to passwords.

After changing the registrar, the AuthInfo code is automatically pre-generated for the new system for security reasons. The Registrar may at any time change the AuthInfo code through the Registry Console in the domain details.

How long can I register a domain for and what happens if I change my registrar?

The registration fee for the domain is redeemed at the time of domain registration itself or when prolonging its registration period. The minimum period for registering a domain is 1 year. Extending the domain registration period is possible sometimes and even more (for registrars: directly via the feature in the domain details), but up to the maximum aggregation of the registration period of 10 years (ie if the domain is registered for 3 years, it is possible to extend it for a maximum of +7 years, Ie together 10).

When changing the domain registrar (this is always initiated by the new registrar), it is normally necessary to extend the registration period by at least 1 year (up to a cumulative maximum of 10 years). The exceptions are when the registrar is changed at the time the domain is registered for 10 years. In this case, an extension of zero is required. The second exception is the change of the registrar, when the new registrar becomes SK-NIC.

Can the address of the Registrar serve as a delivery address for the User if he does not have a delivery address in any of the EU, EEA or EEA Member States?

Yes, in this case, it is referred to as “auxiliary / auxiliary” domain contact (by editing the data of that domain). However, in the case of proof of delivery, it is up to the Registrant to perform the service – if it is not possible for the Registrant to deliver traditional postal or postal delivery to that address. An official consignment will not fulfil the condition for its existence (point 2.1 of the new Rules) and may lose the domain.

How will domain statuses changes in the new system?

In the original system, the lifecycle of domains (so called “life cycle”) changed every day from 11:30 am to the next. In the new system, however, the change of status will not take place in one set time but on a continuous basis, with changes being linked to the exact time of registration of that domain.

How can I manage Contacts properly (User)?

Users (contacts) are managed in a new system with a different model than the old ones. While in the old system user data was verified and managed by SK-NIC, under the new rules this is the responsibility of the registrar. The general sharing of user contact details is not permitted, in particular, given the new requirements of European data protection law (known as GDPR), each registrar must manage its own set of contacts.

It is recommended that the registrar maintains only one contact per subject / person – so changing the data of this entity will not require changing the data on all of its domains.

However, it will not be possible to associate the users (contacts) of other registrars. Such a case occurs only when the authorized domain registrar changes – if the new registrar wants to modify the contact details, they must replace them with their own. In order to compare the original domain name data, the AuthInfo code can be used when the domain registrar is changed.

The change of the authorized contact information registrar is not possible.

How do I generate my own AuthInfo code and what is this code for?

An authInfo domain code is a security element of the domain. The AuthInfo code is only visible to the current domain registrar, and it is provided to the holder. An authInfo code is necessary in order to change the domain registrar. When registering each domain, the registrar can determine whether the AuthInfo code for the domain will be automatically generated or manually enter it. The code can be used by a domain owner or New registrar, it is important to ensure that this code is maintained using the highest possible level of security.
The AuthInfo code is not limited by the number of characters, but SK-NIC recommends that you use at least 12 characters, and the code should have both lower and upper case letters, digits and a special characters similar to passwords.

After changing the registrar, the AuthInfo code is automatically pre-generated for the new system for security reasons. The Registrar may at any time change the AuthInfo code through the Registry Console in the domain details.

How do I create custom IDs for my users?

When registering a User in the web interface, the system offers the possibility of automatically generating an ID, but the Registrar may change it, subject to the following conditions:

  1. Allowed ID length is at least 3 and maximum 16 characters,
  2. Characters in upper case are alphabetical alphanumeric without diacritics, digits 0 to 9, and “- /. /:” (Dash, dot, and two-digit).
  3. The identifier must not begin with the KEY prefix: or NS :.

FOR EXAMPLE , ID can be in the example Id27: zp8.4-corPX or MojeIDvSk-nic / 01

When using EPP, the registrar always creates its own ID.

When do I need to manually change the AuthInfo code?

An authInfo code is a security element for the domain. It is used to allow the secure change of domain registrar for the domain. This code is automatically renamed to the new system after the registrar is changed.

Note: when changing a domain owner, by modifying the domain data in the system, the authInfo code will not change. For security reasons the registrar must manually change this code.

Who can become a .SK domain registrar?

Point 9.1 of the Rules says that:

  • The Registrar can only be a legal entity established in one of the Member States of the European Union, in the State of the European Economic Area or in a Member State of the European Free Trade Association, and the natural person who is authorized to do business accordingly applies accordingly.
  • The Registrar may not be in bankruptcy or liquidation, an insolvency or bankruptcy petition may not be denied or revoked for lack of property and may not be in any analogous situation to such situations, for example in a voluntary auction on the basis of a third Persons or in enforceable proceedings,
  • The Registrar must not be suspended,
  • The Registrar or the persons authorized to represent him / her or to take decisions on his / her behalf or to control him / her shall not be convicted of a criminal conviction for fraud, corruption, involvement in a criminal organization, legalization of proceeds from crime or any other unlawful conduct detrimental to the financial interests of the Slovak The European Union, the European Economic Area or the European Free Trade Association,
  • Must be registered as a User.

In practice, this means that the registrar can become a legal entity that has its registered office (note that it is not enough to have just a delivery address!) In one of the Member States of the European Union, in a state forming the European Economic Area or a member of the European Free Trade Association.

The list of all states that meet this condition is listed in the table below.

 

Kód Názov [SK] Názov [EN] EU / EHS / EEA
AT Rakúsko Austria EU, EEA
BE Belgicko Belgium EU, EHS, EEA
BG Bulharsko Bulgaria EU, EEA
BE Belgicko Belgium EU, EHS, EEA
HR Chorvátsko Croatia EU, EEA
CY Cyprus Cyprus EU, EEA
CZ Česká republika Czech Republic EU, EEA
DK Dánsko Denmark EU, EHS, EEA
EE Estónsko Estonia EU, EEA
EU Inštitúcie Európskej únie European Union Institutions EEA
FI Fínsko Finland EU, EEA
FR Francúzsko/td> France EU, EHS, EEA
DE Nemecko Germany EU, EHS, EEA
GR Grécko Greece EU, EHS, EEA
HU Maďarsko Hungary EU, EEA
IS Island Iceland EEA
IE Írsko Ireland EU, EHS, EEA
IT Taliansko Italy EU, EHS, EEA
LV Lotyšsko Latvia EU, EEA
LI Lichtenštanjsko Liechtenstein EEA
LT Litva Lithuania EU, EEA
LU Luxembursko Luxembourg EU, EHS, EEA
MT Malta Malta EU, EEA
NL Holandsko Netherlands EU, EHS, EEA
NO Nórsko Norway EEA
PL Poľsko Poland EU, EEA
PT Portugalsko Portugal EU, EHS, EEA
RO Rumunsko Romania EU, EEA
SK Slovenská republika Slovakia EU, EEA
SI Slovinsko Slovenia EU, EEA
ES Španielsko Spain EU, EHS, EEA
SE Švédsko Sweden EU, EEA
CH Švajčiarsko Switzerland EEA
GB Veľká Británia United Kingdom EU, EHS, EEA

EU – European Union
EHS – European Economic Community
EEA – European Economic Area

Prior to completing the Registrar’s Agreement, the prospective registrar must demonstrate that they meet requirements above.

At the same time, the Registrar must comply with the other conditions above, which he / she will record in the course of his / her application. If the registrar ceases to fulfil any of the above conditions, the registrar’s authorisation will be terminated along with the registrar’s activity.

Who will manage the User contact information under the new rules?

Each user will manage and update their contact information in the new system. Authorized contact information registrar, i.e. The registrar you choose for that task.

Since the current system does not recognize such a registrar’s role, the current user will be the Authorized Contact Information Registrar designated automated by the following key:

  1. If the user has just one authorized registrar (hereinafter referred to as “OPR”), the system designates him as an Aut. The contact information registrar of this.
  2. If a user has more than one OPR, the system will choose the one with the most domains.
  3. If the user has more than one OPR in step 2, the system selects the first in alphabetical order.
  4. OPR, which did not request to move to the new system, is not the standard reason for the algorithm, i. Is selected from other OPRs.
  5. If it is not possible to select either OPR (none requested or user does not have OPR), the system specifies the registrar according to steps 2 and 3 even if OPR is not. If this is not possible, select Auto. The contact data registrar will be in step 6. However, the user has the option to use the F7 form and modify his data until migration. To add to the OPR someone who has requested the transfer. Their current list can be found at a separate web site.
  6. If no registrar can be selected and the user has not filled in (see step 5), Aut. The contact information registrar of this user will become SK-NIC upon migration. Beware, it will be necessary to enter into a new lease agreement with SK-NIC within the next 14 days or change the Aut. The contact information registrar on another.

Payment methods for .SK domain names

In the new system, all payments, and fees use a so-called Credit system. The Registrar will pre-pay the credit, which will automatically reduce it (charge fees) for all paid transactions. Charges are withdrawn from credit immediately upon completion of each paid transaction. The credit will be met by the registrar as needed, with the billing period having a monthly period. The invoice includes a summary of all credit movements for the relevant period (i.e., both increments and all reductions), as well as a precise breakdown of specific fees.

This invoice includes a summary of all credit movements for the relevant period (i.e., both increments and all reductions), as well as a precise breakdown of specific fees charged.

If the registrar does not have sufficient credit to execute a charge, that is, the amount of his credit is lower than the payment for the operation or his credit is zero, the system will not allow this action to take effect. Implementing it is possible only after the credit is increased. A special blocking of charges will occur when the registrar is designated as the debtor, If they do not pay the invoice or possible invoice failure at the specified time.

How long can I register a domain for and what happens if I change my registrar?

The registration fee for the domain is redeemed at the time of domain registration itself or when prolonging its registration period. The minimum period for registering a domain is 1 year. Extending the domain registration period is possible sometimes and even more (for registrars: directly via the feature in the domain details), but up to the maximum aggregation of the registration period of 10 years (ie if the domain is registered for 3 years, it is possible to extend it for a maximum of +7 years, Ie together 10).

When changing the domain registrar (this is always initiated by the new registrar), it is normally necessary to extend the registration period by at least 1 year (up to a cumulative maximum of 10 years). The exceptions are when the registrar is changed at the time the domain is registered for 10 years. In this case, an extension of zero is required. The second exception is the change of the registrar, when the new registrar becomes SK-NIC.

How will domain statuses changes in the new system?

In the original system, the lifecycle of domains (so called “life cycle”) changed every day from 11:30 am to the next. In the new system, however, the change of status will not take place in one set time but on a continuous basis, with changes being linked to the exact time of registration of that domain.

How can I manage Contacts properly (User)?

Users (contacts) are managed in a new system with a different model than the old ones. While in the old system user data was verified and managed by SK-NIC, under the new rules this is the responsibility of the registrar. The general sharing of user contact details is not permitted, in particular, given the new requirements of European data protection law (known as GDPR), each registrar must manage its own set of contacts.

It is recommended that the registrar maintains only one contact per subject / person – so changing the data of this entity will not require changing the data on all of its domains.

However, it will not be possible to associate the users (contacts) of other registrars. Such a case occurs only when the authorized domain registrar changes – if the new registrar wants to modify the contact details, they must replace them with their own. In order to compare the original domain name data, the AuthInfo code can be used when the domain registrar is changed.

The change of the authorized contact information registrar is not possible.

How do I generate my own AuthInfo code and what is this code for?

An authInfo domain code is a security element of the domain. The AuthInfo code is only visible to the current domain registrar, and it is provided to the holder. An authInfo code is necessary in order to change the domain registrar. When registering each domain, the registrar can determine whether the AuthInfo code for the domain will be automatically generated or manually enter it. The code can be used by a domain owner or New registrar, it is important to ensure that this code is maintained using the highest possible level of security.
The AuthInfo code is not limited by the number of characters, but SK-NIC recommends that you use at least 12 characters, and the code should have both lower and upper case letters, digits and a special characters similar to passwords.

After changing the registrar, the AuthInfo code is automatically pre-generated for the new system for security reasons. The Registrar may at any time change the AuthInfo code through the Registry Console in the domain details.

Can the address of the Registrar serve as a delivery address for the User if he does not have a delivery address in any of the EU, EEA or EEA Member States?

Yes, in this case, it is referred to as “auxiliary / auxiliary” domain contact (by editing the data of that domain). However, in the case of proof of delivery, it is up to the Registrant to perform the service – if it is not possible for the Registrant to deliver traditional postal or postal delivery to that address. An official consignment will not fulfil the condition for its existence (point 2.1 of the new Rules) and may lose the domain.

What does linking the User with the Registrar mean in accordance with Section 9.8 of the Rules?

This is the case if it is de-facto the same legal entity (eg internal division or entity or just another named contact acting as a representative of a legal entity). The Registrar may also register domains for the Linked User, but only if it is a domain that meets the “own need” condition.

When do I need to manually change the AuthInfo code?

An authInfo code is a security element for the domain. It is used to allow the secure change of domain registrar for the domain. This code is automatically renamed to the new system after the registrar is changed.

Note: when changing a domain owner, by modifying the domain data in the system, the authInfo code will not change. For security reasons the registrar must manually change this code.

How do I create custom IDs for my users?

When registering a User in the web interface, the system offers the possibility of automatically generating an ID, but the Registrar may change it, subject to the following conditions:

  1. Allowed ID length is at least 3 and maximum 16 characters,
  2. Characters in upper case are alphabetical alphanumeric without diacritics, digits 0 to 9, and “- /. /:” (Dash, dot, and two-digit).
  3. The identifier must not begin with the KEY prefix: or NS :.

FOR EXAMPLE , ID can be in the example Id27: zp8.4-corPX or MojeIDvSk-nic / 01

When using EPP, the registrar always creates its own ID.

Payment methods for .SK domain names

In the new system, all payments, and fees use a so-called Credit system. The Registrar will pre-pay the credit, which will automatically reduce it (charge fees) for all paid transactions. Charges are withdrawn from credit immediately upon completion of each paid transaction. The credit will be met by the registrar as needed, with the billing period having a monthly period. The invoice includes a summary of all credit movements for the relevant period (i.e., both increments and all reductions), as well as a precise breakdown of specific fees.

This invoice includes a summary of all credit movements for the relevant period (i.e., both increments and all reductions), as well as a precise breakdown of specific fees charged.

If the registrar does not have sufficient credit to execute a charge, that is, the amount of his credit is lower than the payment for the operation or his credit is zero, the system will not allow this action to take effect. Implementing it is possible only after the credit is increased. A special blocking of charges will occur when the registrar is designated as the debtor, If they do not pay the invoice or possible invoice failure at the specified time.