Resource Certification System (RPKI)

LACNIC's resource certification system has two modes: delegated and hosted. In delegated mode an organization can implement its own certificate authority, and so maintain its own private key for signing cryptographic material.

Delegated RPKI Service

The delegated Resource Public Key Infrastructure (RPKI) service has been in operation since 18 December 2019. This service is available to all LACNIC members. Those interested in accessing RPKI in delegated mode should send an email to with the following information:

  1. Organization ID (OrgID)
  2. Full name of point of contact
  3. Email address of point of contact

Brazil: Organizations that received their address space from can access the service at

Hosted RPKI Service

The hosted service has been in operation since 1 January 2011. In this mode, member organizations can perform all RPKI architecture related tasks simply through the website available at the following link.
Organizations that received their resources from IAR.MX should access the service using the following link:

System User Manual

Click here to open the System User Manual for complete information on how to manage certificates and ROAs.

For more information, read our FAQ section.

Standardization Activities

The standardization work for RPKI infrastructure is carried out by the Internet Engineering Task Force (IETF). In RFC 4593 the Routing Protocol Security Requirements (RPSEC) working group analyzed security threats to IP routing protocols. This document mentions the falsification of routing information.

In 2007, the IETF established the Secure Inter-Domain Routing (SIDR) working group to create architecture that would allow us to eliminate the threats to inter-domain (or external) routing identified in RFC 4593. The technology to be developed would have to allow incremental deployment.

Specifically, the SIDR working group documented the use of certificates for the delegation of the right to use Internet resources. Its work includes: the specification of RPKI architecture, certification policies, the profile of the certificates that will be issued and various useful cryptographic materials. Before being able to issue RPKI certificates, it was necessary to define extensions to the X.509 certificates to represent IPv4 and IPv6 addresses, and ASNs. The following RFCs are already part of the RPKI specification: RFC 6480 to RFC 6493, RCF 6810 and RFC 6811.

Further information on the work of the SIDR and SIDROPS working groups is available at the following links:

Additional References

RPKI RPKI Trust Anchor

In the context of the RPKI architecture, a Trust Anchor Locator (TAL) is a file that contains information needed for an RPKI validation tool to access the repository location and begin the validation process.
LACNIC's TAL contains two elements:

  1. A URL pointing to LACNIC's RPKI repository
  2. LACNIC's public key, properly encoded



While most validation tools already include the necessary TAL files, in certain cases it may be useful to have the TAL file separately.
This file can be downloaded at:
The TAL file format is specified in documents prepared by the Internet Engineering Task Force (IETF):

  1. RFC 6490
  2. RFC 7730