IRRD 4.4.4
This IRRD instance is authoritative for NTTCOM, INTERNAL,
and mirrors LACNIC, RADB, RIPE, RIPE-NONAUTH, ALTDB, BELL, LEVEL3, APNIC, JPIRR, ARIN, BBOI, TC, AFRINIC, IDNIC, REGISTROBR, CANARIE.
Key resources
-
IRRD documentation (external)
-
Make sure the version you are reading matches with the version of this instance.
-
Object submission
- to submit updates
to RPSL objects. This uses the same format as email submissions.
-
GraphQL query interface
-
This is the newest and most flexible query option, supporting complex RPSL queries
that can combine any set of criteria and supports related object queries,
where you can explore the graph of IRR data. RPSL attributes are returned in a
structured format, which means you do not need to parse RPSL objects in most cases.
Migrating a maintainer
If you have access to an existing maintainer, you can migrate it
to IRRD internal authentication through this portal, after creating an account.
The benefits of IRRD internal authentication are:
-
You can grant access to other users to edit objects maintained by this maintainer.
-
For each user, you can choose whether they are able to add other users
and update the maintainer object itself.
-
You can create API keys for your maintainer with limited permissions,
rather than include your password in emails.
-
This is safer than traditional RPSL authentication, because you can allow users
or processes to update objects, without allowing them to change the access settings.
-
Logins on this interface can be protected with two-factor authentication.
-
You can submit object updates in this interface after logging in,
without entering further maintainer passwords.
-
Existing authentication methods will keep working and can be mixed,
although you are encouraged to remove them.
-
Password hashes are no longer included in RPSL objects.
Other web services
-
Classic whois query interface on
/v1/whois/
-
For example, use
/v1/whois/?q=!v
for a whois query for the current version. The queries and output
are the same as you would run on port 43.
-
WebSocket-based event stream
-
An event stream over WebSocket with push messages for all changes
to IRR objects and an initial download to synchronise state.
This is typically restricted to a limited set of users.
-
Source status page on
/v1/status/
-
This page provides an overview of IRRD's configured sources and their status.
Access to this may be restricted.