You can move a .si domain to a new registrar while reducing the risk of website or email interruption by keeping its current DNS hosting and nameservers in place during the transfer. The registrar change moves management of the registration; it is not, by itself, a DNS-hosting migration. You will need an AuthInfo password (also called an EPP code), and you should submit it promptly because it expires at first use or after no more than 16 days.
What changes during a .si registrar transfer?
A registrar manages the domain registration. DNS hosting stores the records that direct visitors to your website and route email. A registrar transfer changes the company managing the registration; changing DNS hosting or nameservers is a separate operation.
As an Amazon Associate I earn from qualifying purchases.
Register.si’s instructions describe the transfer process, but do not guarantee that every registrar leaves nameserver settings untouched in its account system. Before starting, ask the receiving registrar how it handles existing nameservers and DNS settings. To reduce risk, leave the current DNS service active and avoid changing nameservers as part of the registrar transfer.
Prepare before requesting the AuthInfo password
Check your contact email and domain status
- Make sure the registrant email address is accurate and that you can access it. Register.si says holders are responsible for keeping their data current and warns that an address controlled by a registrar, developer, or hosting provider can leave the holder without control of official communications: Register.si domain-holder guidance.
- Ask your current registrar to check the domain’s status. A “Server transfer prohibited” status blocks a registrar change. Some locked-domain changes may require additional approval; resolve any restriction with the current registrar rather than assuming the transfer can proceed normally. See Register.si domain status descriptions.
Record your DNS setup
Write down the nameservers currently in use and, if practical, save a copy of the active DNS zone. Include website records and email-related MX and TXT records, along with any records used for service verification. This is a precaution for continuity, not a registry-mandated step. Keep the current DNS host and its service active while the registrar change is under way.
#1 Best Overall
Choose a receiving registrar
Check that the provider accepts .si transfers and ask how it collects the AuthInfo password, whether DNS hosting is separate or bundled, and whether the transfer changes nameservers or DNS settings. Register.si maintains an official list of .si registrars. The receiving registrar can confirm its own workflow; registry instructions do not cover every provider’s account controls.
Request and submit the transfer code
- Request the code from your current registrar. Follow its process to create or obtain the domain’s AuthInfo password. Register.si also refers to this credential as an EPP code, EPP password, or authinfo. Its registrar and registrant transfer instructions explain the registry’s procedure.
- Submit the original password to the new registrar. Use the receiving registrar’s secure submission method. The registry distinguishes the original password given to the new registrar from a digest associated with the current registrar.
- Act promptly. The code is valid until it is first used or for a maximum of 16 days. If it expires unused, request a fresh one rather than trying to use the expired code.
- Let the gaining registrar submit the change. Under Register.si’s general terms, the future registrar submits the application and the current registrar cooperates. The registrar change does not alter the domain’s registration period: Register.si general terms and conditions, clauses 6.3.1–6.3.3.
This procedure changes the registrar, not the domain holder. A transfer of ownership or registrant is a separate process with its own consent requirements.
Keep the website and email on the existing DNS during the move
While the registrar change completes, keep the current nameservers delegated and the existing DNS hosting active. That keeps the website and mail pointed at the same DNS service instead of combining two changes with different failure points. It reduces risk, but it is not a guarantee of zero downtime.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Do not assume that a transfer will preserve nameserver settings in every registrar’s control panel. Confirm the receiving registrar’s behavior before submitting the code, and check that the current DNS host will remain available after the registrar account changes. Register.si’s registrar-transfer and general-terms pages address the registration procedure, while ARNES domain guidance treats DNS management separately.
If you also need to move DNS hosting
Handle that as a separate migration, preferably after the registrar change is complete and stable. Recreate the full DNS zone at the new provider and verify it before changing nameservers. Check applicable A, AAAA, and CNAME records for web services, MX records for mail, and TXT records used for SPF, DKIM, DMARC, or service verification. The .si registry pages do not prescribe this zone-migration checklist; it is operational guidance to avoid losing records when changing DNS providers.
Verify the transfer after it completes
- Check the holder contact email for Register.si’s automatic notification that the registrar change has completed.
- Confirm that the domain still uses the expected nameservers and that the DNS records resolve as intended.
- Open the website and test the email addresses and services that depend on the domain.
- Keep the existing renewal schedule in your calendar. The registrar change does not reset or extend the registration period.
The registry’s completion email confirms notification of a registrar change; it does not certify that your website, mail, or every DNS record is working. Test those services separately.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common reasons a transfer can stall
- Transfer-prohibited status: Ask the current registrar to explain and resolve the “Server transfer prohibited” status before trying again.
- Expired AuthInfo password: Request a new code if the old one was not used within its validity window.
- Uncontrolled registrant email: Update the contact details and ensure you can receive official messages at the holder’s address.
- Unexpected DNS changes: Contact the receiving registrar if nameservers or DNS settings changed, and verify the active zone and delegation. Do not remove the old DNS service until the new setup is confirmed.
Register.si’s published instructions establish the roles of the gaining and current registrar, but they do not set one processing-time guarantee for every .si registrar. Ask the providers involved for the status of a delayed transfer rather than relying on an assumed completion time.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
