Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →You can move a .si domain to a new registrar while keeping your website and email online by leaving your existing DNS hosting and nameservers in place during the transfer. Request an AuthInfo (also called an EPP) code from your current registrar, submit the original code through the new registrar’s process, and verify the domain and services after the registry confirms the change. This reduces risk, but no universal processing time or zero-downtime guarantee is established for every .si registrar.
What changes in a registrar transfer—and what does not
A registrar manages the domain registration. DNS hosting is a separate service that publishes records directing visitors and email to the right servers. Changing registrars does not require changing DNS providers or nameservers. Keeping those services untouched avoids combining two changes that could affect your website or email.
Register.si’s registrar-transfer instructions describe the registry process, while ARNES explains DNS management separately. The registry does not promise that every registrar’s account system will preserve nameserver settings automatically, so confirm the receiving provider’s behavior before proceeding.
Prepare before requesting the AuthInfo code
- Check the registrant contact email. Make sure it is accurate and that you can receive messages there. 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 access to official communications. See its holder information.
- Check the domain status. A “Server transfer prohibited” status prevents a registrar change. Ask the current registrar to resolve it before requesting a routine transfer. Some locked-domain changes may require additional checks or written requests; consult the registry’s domain-status descriptions.
- Record your current DNS setup. Note the nameservers and, if possible, save a copy of the active DNS zone. Include website records and email-related MX and TXT records. Keeping the current DNS service active is the key continuity measure; a zone copy helps with recovery if settings are unexpectedly changed.
- Choose a receiving registrar. Confirm it accepts .si transfers, how it handles AuthInfo submission, whether DNS hosting is included or separate, and how it treats existing nameservers. You can start with Register.si’s official registrar list.
Transfer the registration
- Request the code from your current registrar. The registry calls it an AuthInfo password; it is also known as an EPP code, EPP password, or authinfo. Follow the current registrar’s process to generate or obtain it.
- Submit the original code to the new registrar. Use the receiving registrar’s secure submission method. Register.si’s instructions distinguish the original password given to the new registrar from a digest associated with the current registrar; do not submit a digest in place of the original code.
- Start promptly. The code is valid until first use or for a maximum of 16 days, according to Register.si. If it expires unused, request a fresh one rather than trying to reuse it.
- Let the gaining registrar submit the change. Under Register.si’s general terms, the gaining registrar submits the application and the current registrar must cooperate. The holder’s right to change registrars and these roles are set out in clauses 6.3.1–6.3.3 of the .si general terms and conditions.
The code authorizes a registrar change; it is not a transfer of the domain to a different registrant. A change of holder has separate consent steps in the registry’s transfer guidance.
#1 Best Overall
Keep the website and email running during the move
Leave the existing nameservers and DNS hosting service active while the registration change is in progress. Do not change nameservers just because you have changed registrars. Keeping the same DNS service in place means the web and mail records continue to be served from the existing zone while the registration is handled separately.
If you also want to move DNS hosting, make it a distinct change. First recreate and check the full zone at the new DNS provider, including applicable A, AAAA, and CNAME records, plus MX and TXT records for mail, SPF, DKIM, DMARC, and service verification. Only change nameserver delegation after confirming the new provider serves the required records. These migration checks are operational precautions, not a .si registry-prescribed checklist.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify completion and services
- Look for Register.si’s automatic completion email at the holder contact address.
- Check that the domain still uses the expected nameservers and that the website loads.
- Test sending and receiving email, and check any critical domain-based verification services.
- Keep the existing renewal schedule: changing registrar does not alter the domain’s registration period, according to the general terms.
The registry’s completion email confirms a registrar-change notification; it does not certify that your website, email, or DNS records have been tested. The official sources do not specify a universal processing duration, so rely on the receiving registrar for its workflow and status updates.
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.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches
