Knowledge Base

Check for answers to your questions by searching by keywords, or check categories below.

.be

This article describes the procedures and requirements of .be domain names.
Click on the subject below to open the dropdown for more information.

Successful domain registration requires:

  • two or more nameservers or a nameserver group
  • registrant data needs to be real and valid. Fake data may lead to suspension by the registry.

Successful domain transfer requires:

  • two or more nameservers or a nameserver group
  • an authorisation code provided by:
    • in case of external transfer - the .be registry > www.dnsbelgium.be
    • in case of internal transfer* - the current Openprovider reseller

The authorization code provided by the registry is valid for 7 days.

*Notification is shown in RCP when internal transfer applies.
Follow the internal transfer steps, as an external transfer-code will not work with internal transfers.



Additional notes on a .be transfer

  • Transfer from quarantine is possible, additional costs apply. Contact our Support department for more information.
  • In the rare case that a .be registrar stops its business, its domains will be transferred to a special registrar account of DNS Belgium. Transfers from this account will not restart their registration period; instead, the expiration date will remain unchanged.
  • A bulk transfer is possible, more information can be found here.

Authorization code required yes
Method of confirmation authcode
Registration period after transfer restarts
Average transfer time Realtime
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .be domains is available.
  • External authorization code request - via RCP, API and directly at the registry
  • External authorization code delivery - sent by .be registry only to the registrant
  • External authorization code reset - not possible
  • Internal authorization code request - via RCP and API
  • Internal authorization code delivery - visible in RCP, API

Owner change (trade)

Other update

  • processed realtime
  • registrant can not be updated, trade is required.

The following rules apply in order to decide whether a trade or normal update is required:

    • Organization to a different organization: trade (also if it's only the trading name that changes)
    • Organization to a private individual: trade (also if the private individual was the previous contact person of the organization)
    • Organization to the same organization, but another contact name: regular update (also if other contact data, like address or e-mail, changes)
    • Private individual to a different private individual: trade
    • Private individual to an organization: trade (also if the organization's contact is similar to the previous private individual)

Delete

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

Restore / reactivate

  • restore / reactivation supported via RCP or API
  • Quarantine period can be found under Detailed extension information > Technical information > Quarantine period
Registry
Technical information
  • DNSSEC support: yes
  • Minimum length: 2 characters
  • Maximum length: 63 characters
  • Allowed characters: a-z 0-9 -
  • IDN: no
  • Transfercode is 7 days valid
  • Registration period: 1 year
  • Renewal date offset: 2 days
    The number of days before the registry's expiration date, that Openprovider requires the domain to be renewed or expired. More info.
  • Soft quarantine period: n/a days
    During this period, following after an expiration, the domain can be restored for free. This period does not apply if the domain is deleted explicitly. More info.
  • Quarantine period: 40 days
    During this period, an expired or deleted domain name can be reactivated at an additional fee.
Restrictions
  • Local presence required? no
  • Does Openprovider provide local presence services? n/a
  • Local activity required? no
  • Correct nameserver configuration required? no
  • The Domain(s) can be registered without further limitations.
  • Please always indicate real data of registrant, avoid setting ZIP as '000000', address as 'german german', always use real and correct state, province, city. Do not set fake data to avoid domain revocation. If you use fake data registry may suspend your domain until registry receive real documents proving your ID. Domain owner will receive email notification in a case of fake data usage.
Policies
  • Terms and conditions: http://www.dns.be/en/library/documents/enduser_terms_conditions
  • Dispute policy: http://www.dns.be/en/legal/domain_name_disputes/
Registration agreement The registry requires that a registration agreement is in place between the provider and the domain holder. The text of this registration agreement and any required supplements is the following:
Was this article helpful?
1 out of 2 found this helpful