ISNIC RDAP Interface Specification

Introduction

ISNIC has partially implemented RDAP and some non standard RDAP like queries.

Production environment

The RDAP server is running at rdap.isnic.is port 443.

Development environment

None. As of yet

Document history

Show complete changelog.

Standard

Lookups

Domain lookup

curl https://rdap.isnic.is/rdap/domain/dæmi.is

Note: that this function is rate limited at 50 requests per 30 min. Also note the rate limit does not apply when looking up domains connected to current logged in contact.

Entity lookup

curl https://rdap.isnic.is/rdap/entity/ISHM-IS

Note: that this function is rate limited at 50 requests per 30 min.

Nameserver lookup

curl https://rdap.isnic.is/rdap/nameserver/aker.isnic.is

Note: that this function is rate limited at 1500 requests per hour.

Non standard

ISNIC has implemented a lookup that is not in the RFC7483 but returns non standard lists of domains.

Lists

Isp stat list

ISNIC did for many years before 1. okt. 2018 send a monthly email to registered DNS service providers. This email contained a list of domains delegated by ISNIC to any of the DNSP's registered nameservers, including additional information on the domain status and the registrants and billing contacts 'kennitala'.

Note this function does not return 'kennitala'.

You can test this by first issuing an API KEY here. then accessing the endpoint with basic authentication with the your NIC handle as user and the API KEY as password.

curl -u "YOURHANDLE-IS:APIKEY" https://rdap.isnic.is/rdap/lists/ispstat

You can also use basic authentication with your NIC handle as user and use your password as password at https://rdap.isnic.is/rdap/lists/ispstat (this does not work when TOTP 2FA is enabled, then you need to use an API KEY).

{
	"rdapConformance": [
		"rdap_level_0"
	],
	"domainSearchResults": [
		{
			"objectClassName": "domain",
			"handle": "5125D-IS",
			"ldhName": "isnic.is",
			"unicodeName": "isnic.is",
			"status": [
				"active"
			],
			"nameservers": [
				{
					"objectClassName": "nameserver",
					"ldhName": "ns1.isnic.is"
				},
				{
					"objectClassName": "nameserver",
					"ldhName": "ns2.isnic.is"},
				{
					"objectClassName": "nameserver",
					"ldhName": "ns3.isnic.is"
				}
			],
			"entities": [
				{
					"objectClassName": "entity",
					"handle": "ISHM-IS",
					"roles": [
						"registrant",
						"billing"
					]
				}
			]
		}
	]
}

My domains

Fetch list of domains where connected to logged in contact is either registrant, admin-, billing- or tech contact.

You can test this by first issuing an API KEY here. then accessing the endpoint with basic authentication with the your NIC handle as user and the API KEY as password.

curl -u "YOURHANDLE-IS:APIKEY" https://rdap.isnic.is/rdap/lists/my_domains

You can also use basic authentication with your NIC handle as user and use your password as password at https://rdap.isnic.is/rdap/lists/my_domains (this does not work when TOTP 2FA is enabled, then you need to use an API KEY).

Domain availabilty check

To check if a domain is available use https://rdap.isnic.is/rdap/dac/<DOMAIN TO CHECK>.

Note: that this function is rate limited at 7200 requests per 30 min.

Where the <DOMAIN TO CHECK> variable is the domain in ASCII or IDNA.

The http status codes returned can be

• 200 is not available (domain exists, is pending or is invalid)
• 404 is available
• 408 timeout
• 429 ratelimit
• 500 error

curl https://rdap.isnic.is/rdap/dac/ísnic.is

{
  "rdapConformance": [
    "rdap_level_0",
    "isnic_dac_0"
  ],
  "objectClassName": "domain",
  "ldhName":	"xn--snic-upa.is",
  "unicodeName":	"ísnic.is",
  "status": [
    "active"
  ]
}				

curl https://rdap.isnic.is/rdap/dac/isnic_does_not_exist.is

{
  "errorCode": 404,
  "description": [
    "available"
  ]
}