Registrant verification[Link]


From 16 November 2020, we activated our project Registrant Verification for .be domain names.

Every new domain name is checked against a series of parameters to determine if it’s a suspicious registration. If the domain name matches several parameters, it’s not delegated and proof of identity is requested.

When verification of identity is received, the domain name is delegated.


The flow for registrant verification is shown in this diagram:

Registrant verification flow - see scenario.

The scenario for registrant verification is as follows:

  1. A new domain name is registered.

  2. The domain name is not delegated if verification is required.

  3. The registrant receives an email to ask for verification.

  4. The registrar receives an EPP poll/CPS message indicating verification is required.

  5. The registrant proves his/her identity.

  6. DNS Belgium approves the documentation.

  7. DNS Belgium returns control of the domain name.

Step by step[Link]

1. A new domain name is registered[Link]

Your client contacts you with the request to register a domain name. The new domain name is checked against a series of parameters to determine if it’s a suspicious registration. If it’s selected, the next steps are executed.


We use a series of parameters that automatically check the registrant’s data. Only if several parameters indicate incorrect or incomplete data, do we intervene. We constantly adjust these parameters in order to remain relevant in the fight against fraud.

2. The domain name is not delegated while verification is pending[Link]

The name servers used at registration are overridden. When the registrant’s data is verified (step 6), the domain name is activated within the hour.

More information for the registrant can be found on our website. Please use this page as a guide for your registrant:

3. The registrant receives an email to ask for verification[Link]

We send an email to the registrant asking for verification:

The email provides a link to our website where the registrant can verify their identity. They can do this by electronic identication methods or by uploading documents to a safe location (see step 5).


If you have chosen to inform the registrant yourself through your Registrar settings, you are responsible for sending the verification url to the registrant yourself. You can retrieve the correct url using info-contact v2.0 (see below).

4. The registrar receives EPP poll/CPS messages indicating verification is required[Link]

You will receive two EPP Poll messages/CPS emails to indicate that registrant verification is required for the domain name:

The domain name is not delegated until the verification documents are received. For every future domain name registered with the same contact handle, you will receive another message ‘Verification required for domain ${domainName}.${tld}’ as long as the contact isn’t verified.

5. The registrant proves his/her identity[Link]

Registrants can prove their identity in two ways, both are accessible through the website:

  • By providing their identity using an electronic identification method.

  • By uploading identity documents to a safe location accessible by our Support team. A list of acceptable documents can be found on our website. DNS Belgium Support will provide feedback to the registrant.

6. DNS Belgium approves the documentation[Link]

DNS Belgium receives the proof of identity.

6a + 6b. If the registrant has uploaded documents to our safe location, they will be checked by DNS Belgium Support staff. If there is an issue or more documents are needed, the registrant will be contacted by DNS Belgium Support. Because of the intervention of our Support staff, this may take up to 5 days.

6c. If the registrant has used an electronic identication method, the domain name is automatically approved and will be active within one hour.

7. DNS Belgium returns control of the domain name[Link]

When the proof of identity is accepted, the registrar is notified via POLL message or CPS email:

The registrant receives an email for all his affected domain names:

The domain name is activated and can be used by the registrant. Any other domain that is registered for this registrant (using the same contact handle) in the future will automatically be approved.


Only new domain names that use the same contact handle will be approved. If you make copies of the registrant contact to create new domain names, the registrant will have to verify again.

What if?[Link]

No documentation is provided[Link]

Do the documents insufficiently prove that the holder data are correct? DNS Belgium Support requests additional information. The domain name remains registered but it can’t be used.

The registrant doesn’t provide us with the necessary documents? The domain name remains registered but it can’t be used.

Any other new domain registered with the same contact handle will also be selected for verification and therefore be delegated to DNS Belgium’s landing page. Domains previously registered with the same contact handle will not be affected.

You want to update the Registrant to comply[Link]

A registrant contact selected for registrant verification has verification status Pending. In this state, any update to the contact is allowed. Normal restrictions don’t apply. You can update the contact via My registrations or EPP.

The domain name is transferred away[Link]

We will look at the status of the new contact used in the transfer transaction. In general, we use the status of the new contact. There is one exception: If the old contact is pending verification and the new contact is unverified, the new contact will be set to pending verification.

The contact is updated[Link]

Contacts that are unverified or pending verification keep their status. Contacts that were verified revert back to unverified and our Support team is notified. They will do a manual check on the updated contact.

Number of attempts[Link]

If a registrant is picked for verification, they can try maximum 3 times. After 3 failed attempts, they are directed to our Support staff who will help them to upload documents for verification to our safe location.

Please help your registrants by updating their contact details to match their identity documents.

Number of verifications[Link]

We want to prevent that one individual could approve all domainnames at the same registrar.

This is why DNS Belgium allows for a maximum number of verifications per individual. If this maximum is reached, the website will show an error message and the individual is asked to contact Support. Our Support staff will determine if the maximum can be adjusted for that specific case. Otherwise another individual must verify the domain name.

You want to inform the registrant yourself[Link]

In case you have chosen to notify your registrant yourself in your Registrar settings, these are the steps you should follow.

The decision to verify the details of a domain name is made at creation, so you will receive a poll message about the domain name and registrant immediately after creation of the domain name. At that time you can use info-contact v2.0 with the registrant contact handle to retrieve the url for the registrant. You can use that url in your client portal or in an email template of your own to inform your registrant.

You want to do the verification yourself[Link]

When you do registrant verification yourself, we can activate the ‘registrant verification at registrar’ - feature. This makes it possible for you to indicate which contacts you have verified yourself.

When the feature is activated, you can indicate verification in a create-contact and an update-contact transaction by using the DNS Belgium extension. Contacts for which you use the extension will get the verification status ‘Verified’. Other contacts can still be selected for registrant verification by DNS Belgium. Already existing contacts will go to verified when they are updated using the extension, including the ones that are in verification pending.

Before registering or transferring a domain you should verify the contact, else it can be selected for registrant verification.

To indicate you have verified the registrant yourself, you have to provide a submission date and a source of verification:

  • Submitted date: date on which the verification was done by the registrar

  • Source: Primary application or documentary evidence used for the verification of the registrant contact data, this must be one from the following list:

Verification source

Related application or documentary evidence


itsme® has been officially recognised by Europe as a reliable means of identification, at high level. The itsme® app fulfils the highest security requirements of eIDAS


the registrant’s national identity card


the registrant’s national passport


the registrant’s residence permit


the registrant’s driving license


the registrant’s international driving license


invoice of a utility company registered in the name or legal entity of the registrant


extract of the UBO database in the legal entity of the registrant


an original notarised deed specifying the name or legal entity of the registrant


an original deed of a legal entity stamped by the court registry specifying the registrant


extract from the chamber of commerce in the legal entity of the registrant


extract of the business register specifying the legal entity of the registrant


licensed certificate of the legal entity of the registrant


contract between you and your client specifying the legal entity of the registrant


the invoice of the LEI publisher and/or the LEI number specifying the legal entity of the registrant


screenshot of the LEI portal specifying the legal entity of the registrant


bank payment in the name or legal entity of the registrant


a statement from the bank confirming that the registrant is the owner of the account, including the contact details of the registrant


a letter established on behalf of the registrant specifying the legal entity of the registrant, the attorney that is entitled to represent or act on behalf of the registrant and dully signed by an authorised representative of the registrant


iDIN is a service provided by Dutch banks that allows consumers to identify themselves at other organisations using their own bank’s secure and trusted login methods


any other document or certificate which unambiguously proves the identity of the registrant and which is not publicly available

For examples on how to use the extension in My registrations and EPP, see the examples below.

To activate this feature on your Tryout account, contact our support staff at

To activate this feature for your Live account, we will need documentation of your verfication process and you need to sign an addendum to your registrar contract. Get in touch with our support staff at to start the onboarding.

The documentation of your verification process should include an accurate and detailed description of your process flow and show us when and how you check your client’s details. We expect at least the following checks:

  • email address

  • name and/or organisation

  • address

We are closely following the conversion of the NIS2 directive into national legislation and we try to anticipate its guidelines. It is possible more checks are needed in the future.

Test data[Link]

See Tryout system.

More information[Link]

My registrations[Link]

All registrant contacts have an extra verification status. When a contact is selected for verification, a banner is shown on top of the ‘View contact’ page and the Verification status of the contact is set to Pending:

Contact view in My registrations

At the bottom of view contact, an extra button is available to request the verification url for this registrant. When you click on this button, the mail to the registrant to request a verification is resent. If you have chosen to inform your registrant yourself, you will see the url and can use it in your own mail templates.

On the domain view, a banner is also shown:

Domain view in My registrations

If registrant verification at registrar is activated, extra input fields are added to the create contact and update contact transaction. You first have to check ‘This contact is verified’ before you can add the details of the verification:

Domain view in My registrations

If you leave these fields empty for a create contact or an update contact, the contact will revert back to verification status ‘Not verified’.


Via EPP, you can use info-contact v2.0 to see the verification status of a contact and the url where the registrant can provide verification, the EPP server will give the following response:

<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:dnsbe="">
    <result code="1000">
      <msg>Command completed successfully</msg>
        <contact:status s="ok"/>
        <contact:postalInfo type="loc">

Using info-domain v2.0, you will see that the nameservers are overridden:

<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:dnsbe="">
    <result code="1000">
      <msg>Command completed successfully</msg>
        <domain:status s="ok"/>
        <domain:contact type="billing">c7780583</domain:contact>
        <domain:contact type="tech">c7780581</domain:contact>
            <dnsbe:nameserversOverridden reason="Pending registrant verification">true</dnsbe:nameserversOverridden>

If registrant verification at registrar is activated, you can add an extension to the create contact and update contact transaction to indicate verification:

<epp xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd urn:ietf:params:xml:ns:contact-1.0 contact-1.0.xsd dnsbe-1.0.xsd" xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi="" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:dnsbe="">
        <contact:postalInfo type="loc">
          <contact:name>Jonathan Smith</contact:name>
          <contact:org>Great Company Inc.</contact:org>
            <contact:street>Greenstreet 23</contact:street>
          <contact:pw>Polar Ice</contact:pw>
            <dnsbe:vat>BE 0123 476 545</dnsbe:vat>
-- verification extension
-- verification extension

Using the extenion without the proper permission will result in an error message and a hitpoint for the registrar.