.si

API commandsRestrictionsIDNNIS2

API Commands

Please find in the following a set of the most commonly used standard API commands in order to register, modify, renew, and transfer a domain name.

AddDomainModifyDomainRenewDomainDeleteDomainTransferDomainRestoreDomain

Domain Registration

(API Command reference » AddDomain)

Command

command         = AddDomain
domain          = yourdomain.si
period          = (INT)
ownercontact0   = (CONTACT)
admincontact0   = (CONTACT)
techcontact0    = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0  = (NAMESERVER)
nameserver1   = (NAMESERVER)

Domain Modification

(API Command reference » ModifyDomain)

Command

command = ModifyDomain
domain  = yourdomain.si

Domain Renewal

(API Command reference » RenewDomain)

Command

command    = RenewDomain
domain     = yourdomain.si
period     = (INT)
expiration = (INT)

Domain Deletion

(API Command reference » DeleteDomain)

Command

COMMAND = DeleteDomain
DOMAIN = yourdomain.si

Domain Transfer

(API Command reference » TransferDomain)

Exception

command = TransferDomain
domain  = yourdomain.si
action  = request
auth    = .......
ownercontact0   = (CONTACT)
admincontact0   = (optional)
techcontact0    = (optional)
billingcontact0 = (optional)
nameserver0  = (optional)
nameserver1   = (optional)
forcerequest    = 1 (optional)

After you have initiated the domain transfer through the RRPproxy, the official Registry sends the request to the Licensee (Registrant) of the domain asking for confirmation.

Optionally, you can specify Admin, Tech or Billing contacts on the request. If you wish to do so, please use FORCEREQUEST=1.

Domain Restore

(API Command reference » RestoreDomain)

Command

command = RestoreDomain
domain  = yourdomain.si

The restore request will be manually processed by our support team. You will be notified by email.

Domain Restrictions

A DNS check is available on the registry website

IDN Information

The registry provides also a charset for IDNs

NIS2

FAQ

Questions	Answers
What are the .SI registrant verification requirements?	The registry requires registrant data to remain accurate, complete and up to date. At least one contact method—email address or telephone number—must be verified. Additional identity and postal address checks may be requested following a risk assessment.
We already use CentralNic Reseller email verification. Is that sufficient for .SI?	Yes. When registering a new .SI domain, the registry requires at least one of the two contact details (email address or telephone number) has to be verified.
When is verification required?	The registry’s policy covers new registrations, transfers, and changes to the registrant’s name, business name or contact details. Verification may also be requested during the registration period following a risk assessment or a report of inaccurate data.
What happens if we cannot verify a .SI registrant?	The email verification is sent to the registrant. This occurs within the 14 days before suspension, one initial email will be sent, followed by 1 reminder 3 days before.
Can existing .SI contacts be selected for additional verification?	Yes. The registry may flag existing contacts for review. Previously completing email verification or recording verification details does not prevent the registry from issuing a review request.
What additional information may need to be verified?	Additional checks may cover the registrant’s identity or the existence of the registered business, together with the accuracy of the registrant’s postal address.
How will we know that a contact has been flagged?	CentralNic Reseller generates an event delivered through email and/or API poll messages, depending on your account settings. Monitor these notifications and any follow-up events.
How do we submit verification details for .SI?	Complete the relevant verification checks and record the details using the existing X-VERIFICATION-* extensions. CentralNic Reseller handles the required registry contact update based on those flags. See the NIS2 Compliance documentation for the parameters.
Do we need to resubmit flags if verification details are already recorded?	No. If the relevant flags are already present when the contact is flagged for review, CentralNic Reseller automatically triggers the registry contact update using the existing details.
How long do we have to act on a registry risk assessment request?	If no action is taken, the affected domain will be placed on serverHold after 21 days. Complete the required verification and record the relevant details promptly. If flags are already present, monitor the follow-up event to check the outcome of the automatic update.
Does ICANN’s annual RDRP email template cover the registry’s NIS2 annual reminder requirement?	Yes.