# Verification

For contacts that contain data about persons or organizations, it is possible to store information that confirms that the accuracy of the data has been verified by the member.

The process of verification is called “verification”. The information that represents the result of the verification is the “verification information”. The verification information is stored in the contact together with the data of a person or organization, but is located in a separate section called the “verification block”.

As a brief example, let's look at the arrangement in a contact as it was transmitted via a K/V order.

    1
    2
    3
    4
    5
    6
    7
    8
    9
    [VerificationInformation]
    VerifiedClaim: name
    VerifiedClaim: address
    VerificationResult: success
    VerificationReference: ABC123/45GHT
    VerificationTimestamp: 2023-11-11T15:36:21+02:00
    VerificationEvidence: idcard
    VerificationMethod: auth
    TrustFramework: de_denic

In the verification information block, which is the contiguous part under “[VerificationInformation]”, various claims (name, address, e-mail) can be verified. There is also information about the verification and procedure used to check the data and other details.

The verification information block looks similar for a contact that was created via an XML request.

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    <verification:verificationInformation xmlns:verification="http://registry.denic.de/verification/5.0" xsi:type="verification:verificationInformationType">
      <verification:verifiedClaims>
        <verification:claim>name</verification:claim>
        <verification:claim>address</verification:claim>
      </verification:verifiedClaims>
      <verification:verificationResult>success</verification:verificationResult>
      <verification:verificationReference>ABC123/45GHT</verification:verificationReference>
      <verification:verificationTimestamp>2023-11-11T15:36:21+02:00</verification:verificationTimestamp>
      <verification:verificationEvidence>idcard</verification:verificationEvidence>
      <verification:verificationMethod>auth</verification:verificationMethod>
      <verification:trustFramework>de_denic</verification:trustFramework>
    </verification:verificationInformation>

- Verification information is part of the address contacts and can be added via a CONTACT CREATE request.

- The verification information can be changed or deleted via a CONTACT UPDATE request.

- Verification information can be added easily or must be added as needed.

  - This is the case when DENIC checks the plausibility of the holder handle, among other things, for certain domain requests and requests verification from the member if anything is unclear. If your domain has multiple owners (multi-holder domain), all contacts must be verified.

- Members are solely responsible for verification. However, DENIC can carry out an audit and obtain an explanation of how the verification is carried out.

More information

More about proofs, claims and methods and how to combine them.
Identity verification – methods, verification and claims

What is the format of XML and K/V? What values are possible? This topic will tell you more.
Verification - Formats, Types, Values