Verification - Formats, Types, Values
A verification information block contains details about the verification. As with the other data for a contact (or domain), it is preceded by a keyword and followed by a valid value. The following tables show what can be combined in which form.
To get started, let's look at excerpts from examples of the C/V and XML orders that contain the verification information block.
[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
<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>
Structure and rules for the verification information block for contacts of the types PERSON and ORG
| K/V Keyword | XML Namespace and Elements | 1st Nesting | 2nd Nesting | Occurrence, min – max per verification information block | Type / Length | Value Range | Description |
|---|---|---|---|---|---|---|---|
|
[VerificationInformation] |
<verification:verificationInformation xmlns:verification="http://registry.denic.de/verification/5.0" xsi:type="verification:verificationInformationType"> <verification:verifiedClaims> <verification:verificationResult> <verification:verificationReference> <verification:verificationTimestamp> <verification:verificationEvidence> <verification:verificationMethod> </verification:verificationInformation> |
- |
- |
Once per verification record |
- |
- |
For K/V: header line that precedes the verification record |
|
- |
- |
<verification:verifiedClaims> <verification:claim> </verification:verifiedClaims> |
- |
- |
- |
- |
- |
| VerifiedClaim | - |
- |
<verification:claim> ... <verification:claim> |
1 - 3 | normalizedString / fixed length due to predefined valued |
claim-rule | "claims" are data that has been verified Special features for e-mail The complete verification information block with all keywords or XML elements and values must be specified for an email, if the result of the email check was negative, in other words, the value is ‘failed’. A subsequent update with the positive value ‘success’ must also be communicated, after a fail. If the value ‘success’ was present at the start of the check, the verification information block for email can be reported. |
| VerificationResult | - |
<verification:verificationResult> ... </verification:verificationResult> |
- |
1 | normalizedString / fixed length due to predefined valued |
result-rule | Notification of the verification result |
| VerificationReference | - |
<verification:verificationReference> ... /verification:verificationReference> |
- |
1 | normalizedString / ength is defined by member |
reference-rule | The content is free text that makes reference to a request number or order number, etc. |
| VerificationTimestamp | - |
<verification:verificationTimestamp> ... </verification:verificationTimestamp> |
- |
1 | date-time | timestamp-rule | Point in time, when the verification was performed |
| VerificationEvidence | - |
<verification:verificationEvidence> ... </verification:verificationEvidence> |
- |
1 | normalizedString / fixed length due to predefined valued |
evidence-rule | Evidence that was checked within the scope of the verification (e.g. for the value "idcard", which corresponds to identity card) |
| VerificationMethod | - |
<verification:verificationMethod> ... </verification:verificationMethod> |
- |
1 | normalizedString / fixed length due to predefined valued |
method-rule | Method used to carry out the verification (e.g. for the value "pvr", which stands for evidencing via "video identification") |
| TrustFramework | - |
<verification:trustFramework> ... </verification:trustFramework> |
- |
1 | normalizedString / fixed length due to predefined valued |
framework-rule | Framework used for the verification At present, only the value "de_denic" exists, others may follow later. |
Rules for the value range
| Rule Name of the Value Range | Value Range | Rules |
|---|---|---|
| claim-rule | email, name, address | No distinction is made between upper and lower case |
| result-rule | succcess, failed | No distinction is made between upper and lower case |
| reference-rule | - | free text |
| timestamp-rule | Year = 0000 - 9999 Month = 01 - 12 Tag = 01-28, 01-29, 01-30, 01-31 (based on month and year) Hour = 00 - 23 Minute = 00 - 59 Second = 00-58, 00-59, 00-60 (based on the Leap second) |
You find a detailed description in the RFC3399: Date and Time on the Internet: Timestamps. The RFC uses the coordinated universal time as the basis for date-time definitions. DENIC expects the "date-time" format described in the RFC at this point. This format is composed of the complete date, consisting of year (y) with four characters, hyphen, month (m) with two characters, and day (d) with two characters. The date is followed by the time, which starts with the letter "T" to separate the two. The date is written in a 24-hour format, consisting of hour (h) with two characters, colon, minute (m) with two characters, colon, and second (s) with two characters. Finally, the time zone is added, introduced by a plus sign, followed by the time zone in hours (h) with two characters and the minute (m) with two characters. Format yyyy-mm-ddThh:mm:ss+mm:ss Example 2024-04-02T14:58:30+02:00 This time is a “date-time” format for Central European Summer Time, which corresponds to the following local time: Date: 02.04.2024, Time: 12:58:30 and Universal Time Coordinated (UTC) with the date: 02.04.2024 and the time: 12:58:30. |
| evidence-rule | idcard, passport, population_register, residence_permit, proof_of_arrival, drivers_licence, company_register company_statement, bank_account, online_payment_account, utility_account, bank_statement, tax_statement, written_attestation, digital_attestation, postal_ver_transaction_log, email_ver_transaction_log, address_database | No distinction is made between upper and lower case |
| method-rule | auth, electronic_document, physical_document, vdig, bvr, pvr, data, reachability | - |
| framework-rule | de_denic | At present, only the predefined text "de.denic" can be entered. In the future, other values may be possible, for instance when other registries operating in the European area offer verification procedures that are accepted by DENIC. By stating the other verification procedure, a member can inform that the claims were already checked and that the processes of DENIC should take this into consideration when processing the request. |
Mapping table for method names to value names
| Proof | Value in the Request |
|---|---|
| eID / eIDAS | auth |
| Electronic document record | electronic_document |
| Physical document record | physical_document |
| PostIdent | vdig |
| Photo-Ident | bvr |
| Video-Ident | pvr |
| Transaction record | data |
| Reachability | reachability |
Claims, verifications and methods that can be combined
-
Multiple claims can occur per verification information.
-
Only one verification and only one method can be specified per verification information block.
| Proof | VerifiedClaim | VerificationEvidence | VerificationMethod (only one method per evidence allowed) |
|---|---|---|---|
| ID card |
|
idcard |
|
| Passport | name | passport |
|
| Population register |
|
population_register |
|
| Residence permit |
|
residence_permit |
|
| Proof of arrival | name | proof_of_arrival |
|
| Driver's license | name | drivers_licence |
|
| Company register |
|
company_register | electronic_document |
| Founding documents |
|
company_statement |
|
| Federal Gazette | name | company_register | electronic_document |
| Record of payment via direct debit / transfer or credit card | name | bank_account | data |
| Record of payment via online payment |
|
online_payment_account | data |
| Utility bill |
|
utility_account |
|
| Bank statement |
|
bank_statement |
|
| Tax statement |
|
tax_statement |
|
| Written confirmation by an already verified natural person |
|
written_attestation | physical_document |
| Digital confirmation by an already verified natural person |
|
digital_attestation | electronic_document |
| Postal transaction log |
|
postal_ver_transaction_log |
|
| E-mail transaction log | email_ver_transaction_log | reachability | |
| Address Database | address | address_database | data |
Copy and paste
For quickly inserting it into your source code, database, etc.
name, address, idcard, auth, vdig, electronic_document, physical_document, bvr, pvr
name, passport, vdig, electronic_document, physical_document, bvr, pvr
name, address, population_register, electronic_document, physical_document, bvr, pvr
name, address, residence_permit, electronic_document, physical_document, bvr, pvr
name, proof_of_arrival, electronic_document, physical_document, bvr, pvr
name, drivers_licence, electronic_document, physical_document, bvr, pvr
name, address, company_register, electronic_document
name, address, company_statement, electronic_document, physical_document
name, company_register, electronic_document
name, bank_account, data
name, address, email, online_payment_account, data
name, address, utility_account, electronic_document, physical_document
name, address, bank_statement, electronic_document, physical_document
name, address, tax_statement, electronic_document, physical_document
name, address, email, written_attestation, physical_document
name, address, email, digital_attestation, electronic_document
name, address, postal_ver_transaction_log, vdig, reachability
email, email_ver_transaction_log, reachability
address, address_database, data
More information
What is verification? This topic gives you some basics to get you started.
Verification
More about proofs, claims and methods and how to combine them.
Identity verification – methods, verification and claims