Requesting Resources By Email

The RIPE NCC has introduced a test facility that replicates the request robot's behaviour. Please read more about this facility in our tools section.

If you do not wish to use the LIR Portal, or if this functionality is not available because you are a Direct Assignment User, you can request resources by email. There are a number of request forms in the RIPE Document Store that will help you create an email that provides us with everything we need to avoid delays in processing your request.

However, if you need to contact Registration Services by email, please use the following mailboxes:

For a full overview of all RIPE NCC email contacts, please refer to this page.

Registry Identifier

Every LIR or Direct Assignment User receives a registry identifier once they have completed the agreement with the RIPE NCC.

The Registry Identifier must be included in every message sent to hostmaster@ripe.net , lir-help@ripe.net. It is used to identify the registry. Each request containing a valid identifier will receive an acknowledgement indicating whether they receive service or not and a ticket number.

Where possible we suggest the inclusion of the identifier in an RFC822 header line of the messages concerned.
The suggested format is: X-NCC-RegID: nn.example. Where it is impossible to modify the RFC822 header, this line can also be included in the body of the message. Please note that the registry identifier needs to be lower case (it is case sensitive).

In accordance with the policies established by the contributors' committee (see ripe-132 for details), the RIPE NCC provides service only to its contributors.

Requests received from contributing LIRs and Direct Assignment Users will be handled in the order in which they are received. Requests from LIRs and Direct Assignment Users that are behind on their payments will not be serviced until the financial situation has been rectified. Requests not accompanied by a valid Registry Identifier will not be processed.

For more information, see RIPE Document: "RIPE NCC Request Tracking and Ticketing" at: http://www.ripe.net/ripe/docs/request-tracking.html

Ticketing System

The RIPE NCC uses a ticketing system to track the history of every request sent to the Registration Services mailboxes. Requests submitted to these role accounts will be notified of the ticket number that has been assigned to the request. The number must be referenced in all subsequent messages related to this request. The ticket number remains valid until the request has been handled. Every new request gets a new ticket number. This means that a LIR should never send two requests in the same message.

Moreover, because a ticket number is associated with a specific request, it should never be re-used.

For more information, see RIPE Document: "RIPE NCC Request Tracking and Ticketing" at: http://www.ripe.net/ripe/docs/request-tracking.html

You can check the status of their ticket on the RIPE NCC web site: http://www.ripe.net/cgi-bin/rttquery

Distribution Robot

The RIPE NCC uses an automatic robot to distribute all messages sent to these role accounts.

For help on interacting with the robot, please see the RIPE NCC web site at: http://www.ripe.net/rs/status.html

PGP Authentication

At the RIPE 40 meeting, a decision was made that all outgoing emails from the RIPE-NCC to the Local Internet Registries should be authenticated. The email that you received from these accounts (mentioned above) have been signed by the RIPE-NCC PGP master key.

RIPE NCC public key