iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can move a .si domain to a new registrar while keeping your website and email online by leaving your DNS hosting and nameservers unchanged during the transfer. First check the domain’s status and registrant email, then obtain an AuthInfo code from the current registrar and submit it to the new one. This reduces risk, but no universal transfer time or zero-downtime guarantee is established for every .si registrar.
What a registrar transfer changes—and what it does not
A registrar manages the domain registration. DNS hosting manages the records that direct visitors to your website and route mail. Moving the registration does not require moving DNS hosting or changing nameservers.
For the lowest-risk move, keep the current DNS provider, nameservers, and active DNS zone in place while the registrar change completes. Register.si documents registrar changes and DNS management separately; it does not promise that every registrar will preserve nameserver settings in its account panel. Ask the receiving registrar how it handles existing nameservers before starting. Register.si’s transfer instructions and ARNES’s domain and DNS guidance explain the separate roles.
PC 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 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePrepare before requesting the AuthInfo code
- Check the domain status. A “Server transfer prohibited” status blocks a registrar change. Ask the current registrar to resolve it before proceeding. Some locked-domain changes may require additional approval. Register.si’s status descriptions explain the relevant statuses.
- Confirm the registrant email. Make sure the holder’s contact address is accurate, accessible, and controlled by the holder. If official messages go to an address controlled by a registrar, developer, or host, you may lose access to important communications. Register.si’s general terms cover holder data responsibilities.
- Record the current DNS setup. Note the nameservers and, if possible, save a copy of the active DNS zone, especially website records and mail-related MX and TXT records. Keeping a copy is a practical safeguard, not a registry-mandated transfer step.
- Choose a receiving registrar. Check that it accepts .si transfers, explains how to submit AuthInfo, and clarifies whether DNS hosting is separate or bundled. Register.si publishes an official registrar list; it does not rank providers or establish their current prices or support quality.
Transfer the .si domain
- Request the code from the current registrar. Ask for or generate the domain’s AuthInfo password. It may also be called an EPP code, EPP password, or authinfo. Follow the current registrar’s process; there is no single control-panel path that applies to all providers.
- Submit the original password to the new registrar. Use the receiving registrar’s secure submission method. Register.si distinguishes the original password supplied for the transfer from a digest associated with the current registrar.
- Act promptly. The code is valid until first use or for a maximum of 16 days, whichever comes first. If it expires unused, request a new one. Register.si’s transfer instructions describe the validity period.
- Let the new registrar submit the transfer. Under Register.si’s general terms, the gaining registrar submits the application and the current registrar cooperates. The registration period does not change. See clauses 6.3.1–6.3.3 of the .si general terms and conditions.
Keep your website and email working
During the registrar move, leave the existing nameservers and DNS hosting active. That keeps the domain delegated to the same DNS service, which continues serving the website and mail records while the registration is being moved. Do not accept or make a nameserver change as part of the registrar transfer unless you intentionally plan a separate DNS migration and have verified the new zone.
#1 Best Overall
If you also need to move DNS hosting, treat it as its own change. Recreate the full zone at the new DNS provider and verify it before changing nameservers. Include applicable A, AAAA, and CNAME records for services, as well as MX and TXT records used for mail, SPF, DKIM, DMARC, and service verification. The .si registry’s transfer instructions do not prescribe a DNS-migration checklist, so confirm the details with both DNS providers.
Verify the change after completion
- Check the holder contact email for Register.si’s automatic notification that the registrar change completed.
- Confirm the domain still uses the intended nameservers and resolves to the expected website.
- Test sending and receiving email, particularly if the domain is used for business or account recovery.
- Keep renewal reminders on the existing schedule: changing registrar does not alter the domain’s registration period.
A registry completion email confirms the registrar-change notification; it does not validate your website, DNS records, or mail delivery. Those services need to be checked separately.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common problems and what to do
- The transfer is blocked: Check for “Server transfer prohibited” or another restriction and contact the current registrar to resolve it.
- The code is rejected or expired: Confirm you supplied the original AuthInfo password, not a digest, and request a fresh code if the existing one has expired.
- You cannot receive transfer messages: Verify the holder email is correct and accessible, then contact the current registrar about updating it.
- The new registrar proposes changing nameservers: Ask whether this is required for registration transfer or simply part of its bundled DNS service. To avoid combining changes, keep the current DNS service active until a separately planned migration is verified.
- You are changing the owner as well: A change of registrar is not a change of registrant. A holder change has separate consent steps under the registry’s transfer guidance.
Register.si’s published process does not establish a universal completion time for all registrars. Confirm provider-specific steps with the receiving registrar, and do not schedule a dependent DNS migration on the assumption that the registration move will finish by a particular deadline.
Recommended Free Tools
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.
