Successful domain registration via RCP (Reseller Control Panel) or XML API or REST API requires:

• two or more nameservers or a nameserver group
• postal box (postbus) is not allowed in the registrant handle
• valid phone number is required in all handles
• (Optional) Reseller in whois option*
• FAX number is not required, but in case it is entered in the handle, it must be valid.

* - When submitting a handle in the field "Reseller handle" this information will be visible in the whois. If you do not want details displayed, leave the field empty.

- When a "Trading Name" is entered in the handle, this name will be displayed in the whois instead of the company name of the handle.

- Starting October 1st 2023, you will no longer be able to purchase Whois Privacy Protection for new .nl domain names due to new SIDN policy. Furthermore, it will not be possible to renew your existing Whois Privacy Protection services for .nl domains. Your active Whois Privacy Protection services for .nl domains will remain active until their expiration date.
When domains are renewed, the WPP will be deactivated automatically. This will trigger an email from SIDN about a change of ownership to the registrant. We can not prevent this email unfortunately.

Successful domain transfer via RCP or XML API or REST API requires:

• an authorisation code that you need to request at your current provider.
• two or more nameservers or a nameserver group
• postal box (postbus) is not allowed in the registrant handle
• valid phone number is required in all handles
• If FAX number is entered (not required?), it must be valid

If you notice that the nameservers or the contacts are not correctly updated after a transfer, the update was not accepted by SIDN due to one of the missing requirements above.
Make sure to correct the data in the used handles, before processing a domain sync or update.

Additional notes on a .nl transfer

• Remaining registration period at the registry will be unchanged. This period might be different then your previous hosting provider communicated in case they renew .nl domains per month or quarter with SIDN instead of per year. In addition, SIDN does not support multiyear renewals. In case your current provider has renewed the domain for more than 1 year, they will not have renewed / paid for this period at SIDN (yet). Only the remaining registration period of SIDN will be unchanged at the moment of transfer.
• An authorization code is not required if the current registrar is bankrupt, contact support for more information.
• Escalation procedure is possible if the current registrar does not provide the authorization code.
• Bulk transfers are possible (more info)
• Transfer from quarantine is possible; additional costs apply. More info here.
• In exceptional cases, SIDN can request us to send the authorization code directly to the domain holder.
• Openprovider does not (yet) support .nl Control. If you want to transfer a domain that runs under .nl Control, please deactivate this at the current registrar before ordering the transfer in Openprovider.
• If registry expiration date is close or expired (<= 1 day), you will have 1 day after activation and Openprovider will enable auto-renew (and notify about that).
  
  

Proof of ownership

In some cases, for example when requesting us to escalate a transfer or to transfer a domain from quarantine, we are obliged to check the ownership of the domain name. The domain holder can request those data from registry SIDN, or you can do so for the domain holder:

• Visit SIDN's website in English or Dutch
• Fill in the domain name, the domain holder's e-mail address and zip code
• SIDN will now send two links to the domain holder and administrative contact:
  • one link for the domain holder himself
  • and one link that can be shared with others
• Do not open the second link (as it can be opened only once!), but send it to Openprovider
• Openprovider is now able to validate the owner details

• Authorization code request - via RCP (Reseller Control Panel) or XML API or REST API 
• Authorization code reset - not possible
  

Owner change (trade)

• requested as a normal domain update via RCP or XML API or REST API
• processed realtime

Other update

• requested via RCP or XML API or REST API
• processed realtime

If you notice that the nameservers or the contacts are not correctly updated after a transfer, the update was not accepted by SIDN due to one of the missing requirements above.
Make sure to correct the data in the used handles, before processing a domain update.

Pledged domains (Domeinen met pandrecht)
In case you receive the error "This transaction is incompatible with the domain name's current status" it can indicate that the domain is Pledged (pandrecht). This is a service between SIDN and the registrant directly.

When requesting an update for a pledge domain, the registry will not directly process them realtime, but they will be handled manually. This can take 1 till 3 days.
The error "This transaction is incompatible with the domain name's current status" is shown because we do not get a direct response from the registry back that the update is successful or not. The request is actually pending at the registry.

Owner update: SIDN need approval of the pledgee within 3 days.
Nameserver change: SIDN will process this within 1 workday.

Delete

• requested via RCP or XML API or REST API
• processed realtime
• will result in a quarantine period

In case error is shown "Cannot delete domain on registry side" the domain is limited (Pledged / pandrecht). Please contact the registrant and / or SIDN to resolve this.

In case the registry does not allow a domain deletion, we can request a special cancellation procedure with the registry. The fee for this procedure is €25,00 per domain name. Contact our support department for more information and to start the procedure.

Restore / reactivate

• restore / reactivation supported via RCP or XML API or REST API
• quarantine period can be found under
  Detailed extension information > Technical information > Quarantine period