🇸🇮 .si — Slovenia

The .si is a country-code top-level domain (ccTLD) operated by Academic and Research Network of Slovenia (Arnes). This article documents the technical, operational, and contractual requirements for the TLD, along with special considerations for registry, registrar, and domain management.

General Information

Property Value
TLD Type ccTLD
Registry Academic and Research Network of Slovenia (Arnes)
Registry Country Slovenia
Registry Website www.register.si
Provisioning Protocol EPP
Second-Level Registration ❌ No
Accreditation Required ✅ Yes

Domain Lifecycle

Property Value
Registration Period 1–5 years
Renewal Period 1–5 years
Transfer Renewal Period 1 year
Deletion Policy Immediate
Auto-Renew Enabled ❌ No
Auto-Renewal Before Expiry On expiration
Sync After Operations registration, transfer

Grace periods

Period Duration
Add Grace Period 16 days
Standard Grace Period 30 days
Redemption Period 30 days
Pending Restore 0 days
Pending Delete 5 days

Launch Phases & Availability

Property Value
General Availability ✅ TLD is live
TMCH / Trademark Claims ❌ No

Domain Characteristics

Property Value
Domain Length 2–63 characters
IDN Support ❌ No
Premium Domains ❌ No
Reserved Domains ❌ No
Registry Lock ❌ No

Contacts & Roles

Property Value
Required Contacts Domain Owner, Technical Contact
Supported Roles Domain Owner, Technical Contact
Thick WHOIS ✅ Yes
Privacy Proxy Allowed ❌ No
Contacts Transferable ❌ No
Allowed Postal Types International
AuthInfo Required ✅ Yes (1–255 characters)

Nameservers & DNS

Property Value
Nameserver Count 2–10
Host Objects Allowed ✅ Yes
Registry Nameserver Check ✅ Yes
DNSSEC Allowed ✅ Yes
DNSSEC Required ❌ No
DNSSEC Mode DS
CZDS (Zone Download) ❌ No

Transfer Policy

Property Value
Transfer Lock Enabled ✅ Yes (0 days after registration; 0 days after transfer)
Transfer Duration 0 days
Transfer Extends Domain ❌ No
Transfer via AuthInfo ❌ No
Confirmation Required ❌ No

WHOIS & RDAP

Property Value
WHOIS Server whois.register.si

Dispute Resolution

Property Value
Dispute Resolution Available ❌ No

Implementation Notes

  • Ensure complete TLS/SSL configuration for every registry environment.
  • Enable DNSSEC wherever the registry supports it.
  • Make sure AuthInfo/transfer secrets meet the registry's length and format requirements.
  • Review the registry's supported domain statuses and dispute-resolution policies before launch.