Updates

15.05.2025

No quota points are used for QUEUE-READ and QUEUE-DELETE requests

Previously, DENIC did not charge quota points for LOGIN and LOGOUT requests. This will remain the case. READ-QUEUE and DELETE-QUEUE requests have been added to the list of requests for which no quota points will be charged. The relevant topic, Quotas and Registration Accounts, has been updated with a notice in the first paragraph.

 

17.04.2025

Message codes 16350000040 and 16350000041 for message type domainStatusUpdate revised

In previous versions of the two message codes, the description texts were supplemented with a date for de-delegation and a date for deletion. In the new versions, a note has been added to the data to indicate for which claim or claims verification is required. In addition, the keywords “Date:” and “VerificationClaims:” appear before the data and the claim(s). The following examples illustrate the changes.

 

Previously, the information in K/V and XML looked as follows:

 

 

The new versions look like this:

 

 

You can find the complete and updated examples here Message Type domainStatusUpdate.

 

17.04.2025

Message code 63200041865 revised – more information added

The message code occurs in two variants of an error. In the second variant, the description text has been revised.

Previous description

What is this about? In the second variant of the error, multiple verification information blocks were specified. The same claim was specified in at least two verification information blocks, for example, the claim “name.” The duplicate is recognized by the fact that the verification information:

• VerificationResult,

• VerificationReference,

• VerificationTimestamp,

• VerificationEvidence,

• VerificationMethod und

• TrustFramework,

or more precisely, their values, are also identical in both verification information blocks.

It does not matter that “VerifiedClaim: address” was additionally specified in the first verification information block. The decisive factors are the values from “VerificationResult” to “TrustFramework,” which form a unique pattern that must only appear once in a verification information block.

The updated description can be found under message code 63200041865 in the topic List of Message Codes for Verification.

 

15.04.2025

Table of contents for NIS 2 closed

The table of contents for NIS 2 has been closed and most of the content has been added to DENIC-29. I have broken down the distribution of content across the other topics for you in this image.

 

03.03.2025

NIS 2

Specifying a Telephone Number as a Dummy

The topic Information on the Phone Number has been revised.

• Due to the legal situation, members can choose whether to provide a valid phone number or a dummy phone number for a contact.

• The format of the dummy phone number consists of the country code and the phone number, which consists only of zeros (0).

• The phone numbers or dummy phone numbers must be specified in the K/V or XML order.

• Specifying a dummy phone number is only possible on a temporary basis.

• In the future, DENIC will only accept valid phone numbers, which will be checked using the completeness check. All requests sent with a dummy phone number will be rejected by DENIC.

• DENIC will announce the date on which only valid phone numbers will be accepted via the usual information channels.

More detailed information with examples is described in the topic.

 

25.11.2024

NIS 2

Table of Test Scenarios revised

Additional descriptions have been added to the topic that explain what can be tried using the ready-made tests.

Figure 1:  Excerpt from the additional examples

In addition to the newly designed table, sample orders have been added. The examples can be used to try out the test scenarios from the table.

Figure 2:  Excerpt from the revised table

Figure 3:  Excerpt from the examples

 

NIS 2

Examples added for CREATE-AUTHINFO1 and CREATE-AUTHINFO2

Examples have been added (CREATE-AUTHINFO1 and CREATE-AUTHINFO2).

 

NIS 2

Telephone Note Updated for Domain RESTORE

Link: Domain RESTORE

Figure 4:  The marked part is new.

 

NIS 2

Information about Phone and Email added

Link: Information on the Phone Number and Email

Figure 5:  Excerpt from the topic

 

22.11.2024

NIS 2

PERSON and ORG can be changed

The types of the contact, PERSON and ORG, can be changed if there is no DISPUTE on the domain. Changing the verification information also works with DISPUTE, see Contact UPDATE.

 

NIS 2

Domain CREATE and Domain UPDATE Response with “pendingCreate”

Domain CREATE and Domain UPDATE responses include a pendingCreate status.

 

NIS 2

Deadline Information for Domain CHHOLDER Responses

Domain CHHOLDER responses indicate deadlines if the domain needs to be verified.

 

30.09.2024

NIS 2

Update of Error Table with new Error Messages for Domain CREATE/CHHOLDER/CHPROV/RESTORE

The error table has been updated with error messages for domain orders, see Error Messages.

 

NIS 2

Extension of the Description of Domain INFO

The information on Domain INFO has been extended with further examples and information.

 

NIS 2

Examples of Notifications in the Message Queue and for Emails

The RRI Messages section has been added.

 

NIS 2

Error Messages related to Verification Information

A section for syntax errors in the verification information has been added to the error table.

 

NIS 2

New Domain Status added

The new domain statuses Domain Statuses pendingCreate and serverHold have been added.

 

27.09.2024

NIS 2

Update on the Error Table with new Error Messages for Contact CREATE and Contact UPDATE

The Error Messages contain new errors that can occur with a phone number.

 

NIS 2

Added K/V and XML Examples for Contact Responses

The Contact CREATE, Contact INFO and Contact UPDATE topics now include examples of both formats.

 

NIS 2

Updated Domain INFO Responses in K/V format

A comparison table in the topic Domain INFO shows the output for:

• your own domain, recursive,

• your own domain, non-recursive,

• third-party domain, recursive, with AuthInfo,

• third-party domain, recursive, without AuthInfo and

• third-party domain, non-recursive, without AuthInfo.

 

25.09.2024

Code Examples with Numbering and Copy Button

The code examples have been made clearer and more convenient to use. There is a button in the top right-hand corner that can be used to copy the content to the clipboard. The numbering in the margin makes it easier to identify individual lines. If you have a question about an example, you can include the lines.

Figure 6:  Excerpt of a code example

 

NIS 2

Table with Test Scenarios added

A table of test scenarios (Mock-Up Tests) for the test environment was added to try out the new processes in the RRI.

Figure 7:  Excerpt from the table of test scenarios

 

NIS 2

Update to the Error Table with amended Error Messages

The table of Error Messages has been extended. Known message codes have been added for which the error texts have been reformulated.

Figure 8:  Table with the extended error messages

 

23.08.2024

NIS 2

Expansion of the chapter ‘04 Verification’

In addition to the descriptions of the verification procedures and verifications, topics have been added that explain the values and show the combination of values in the verification information. There is also a small preview for telephone number verification in the form of an example.

 

NIS 2

Preview for chapter ‘02 Completeness check’

The chapter still needs to be reviewed, but we are already showing some information in a table.

 

05.07.2024

NIS 2

Error table added

An error table with Error Messages has been added, new error messages will be added continuously.