ARIN’s Operational Test and Evaluation environment (OT&E)


OT&E is an environment containing a copy of production-like data that allows developers to experiment with ARIN interactions without affecting production data. ARIN’s OT&E does not support email-based interactions, but allows for experimentation with three main ARIN services:

Note: OT&E exists solely for experimental usage and research, and is not linked to ARIN’s production system.

Accessing OT&E

To request access to OT&E, log into your ARIN Online account and use Ask ARIN to request access to the environment using “Other” as the message topic. Once vetted, ARIN will grant OT&E environment access and send additional usage instructions. ARIN encourages all OT&E users to arin-tech-discuss mailing list for information sharing and outage information.

OT&E Hosts

The following URLs should be used when interacting with ARIN’s OT&E services in place of their production counterparts.

API Keys

OT&E services require Application Programming Interface (API) keys. To create an API Key:

  • Log into ARIN Online
  • Select WEB ACCOUNT on the left
  • Find the API Key Management area
  • Select Create API Key

Note: OT&E data is refreshed on the first Monday of each month to mirror production. If you created an API key in production since the last refresh, you must create a separate one within OT&E to use until the next refresh occurs.


Whois-RWS functionality within OT&E is a mirror of production. Remember to use in place of For more information on Whois-RWS usage, visit ARIN’s Whois-RWS page.


Reg-RWS functionality within OT&E is a mirror of production. Remember to use or as RESTful calls to or will affect production data. For more information on Reg-RWS usage, visit ARIN’s RESTful Interfaces page.


ARIN resource holders may request certificates and manage Route Origin Authorizations (ROAs) within OT&E, using the same methods as production. OT&E also contains a repository of certificates and ROAs, and handles key rollovers and revocations. For more information on RPKI usage, visit ARIN’s RPKI Home Page. For ROA Request signing instructions, visit the RPKI FAQ page.

Note: OT&E ROA Requests should be signed using a SEPARATE ROA Request Generation Key Pair than the one you use in production.

In order to validate using ARIN’s OT&E data, you will have to use the following Trust Anchor Locator (TAL). Note that this TAL differs from the production TAL:




The OT&E TALmust then be plugged into an RPKI validator to allow for the fetching and validation of ARIN OT&E repository objects. ARIN recommends the following validators:


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s