Contact types[Link]

All contacts have to be created upfront. You will only need to enter the ‘ALIAS’ (=unique identifier) for this person in a transaction form. Every alias is unique over the whole system, i.e. they can’t be used by different registrars

There are 4 types of contacts:


The billing contact is required when you want to register a domain name. It is the person/department to whom the invoices are sent. The language of the invoices is in the language of the billing contact’s choice. Exactly 1 billing contact can be created per registrar.

Technical or onsite[Link]

At least 1 technical contact must be associated to each domain name. This is the person to contact in case of a technical problem.

  • You should choose the type ‘onsite’ when the technical contact is from the organisation of the registrant or from a third party (like an intermediate website builder). Maximum 5 contacts of type ‘onsite’ can be associated with a domain name.

  • In case the registrant does not have any technical knowledge, then you should link a technical contact of your own organisation (the registrar) to the domain name. To define such a contact, you need to specify ‘tech’ as the type. Maximum 10 contacts of type ‘tech’ can be registered in total per registrar. Maximum 5 contacts of type ‘tech’ can be associated with a domain name.


.be domain names can be registered by everyone. This means the registrant can be a private person or an organisation. It is very important this distinction is made, because it has a certain legal consequence. Furthermore, there is a restriction to updating registrants, because the identity has to remain the same.

In general, the registrant is responsible for the domain name. In case of a conflict this is the person/organisation who will be contacted. All address information and the e-mail address of the registrant should be correct and accurate and should belong to your client. If this contact cannot be reached the domain name can be revoked!

  • Private person: The ‘Organisation’ field must be left empty. The ‘Name’ field should contain the ‘firstname lastname’ of the private person. Domain names registered for this registrant are personal domain names, therefore it is not possible to change the name of the registrant by means of an update!

  • Organisation: The ‘Organisation’ field must be filled in with the correct company/organisation name. The ‘Name’ field can be left empty, but it is advisable to fill in the name of the responsible person within the organisation. Feel free to use terms as ‘Department, ‘Director’, ‘Chairman’, etc. … Similar to personal domain names, it is not possible to change the organisation field by means of an update. Although it is possible to change the ‘name’ field, because responsible persons tend to change within certain organisations or companies.

If you want to change the identity of the registrant, you need to initiate a transfer transaction. If there is an error in the identity of the registrant, it could be resolved by using the monitored update transaction as will be explained further. However, small changes are allowed, for instance changing upper to lower case and vice versa and changing the word order.


One contact person should have one alias! Don’t create aliases you don’t use/need!

Please don’t pollute the DNS Belgium database unnecessarily by creating several aliases for the same contact person. This will also make it harder for you to group domain names per customer. We also explicitly ask that you don’t create contact aliases that you don’t use. This is not only polluting our database but - if done in large or even excessive numbers - can have a negative impact on the database performance.

If DNS Belgium notices abusive behaviour by a registrar creating a lot of unnecessary contact aliases, it can decide to block that registrar’s account in order to protect the integrity of its database and the overall performance of the database.

Country codes[Link]

When creating a contact, you need to specify its country code. The codes used are specified in the ISO 3166-1 list with a few additional codes from the ISO 3166 reserved codes list.