-
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
101 lines (74 loc) · 7.64 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
---
title: ""
layout: page
stylesheets:
- /assets/style.css?v=202407161206
---
<form action="https://client.rdap.org" method="GET" class="form-inline">
<div class="col" style="padding:0">
<div class="input-group">
<input class="form-control" id="object" type="text" name="object" placeholder="example.com, 196.168.0.1, 2001:db8::/32, AS64496, etc" required>
<div class="input-group-append">
<input class="btn btn-primary" type="submit" value="Submit">
</div>
</div>
</div>
</form>
<br>
<p>The <strong>Registration Data Access Protocol (RDAP)</strong> is the successor to <a href="https://whois.icann.org/en/about-whois">WHOIS</a>. Like WHOIS, RDAP provides access to information about Internet resources (<a href="https://en.wikipedia.org/wiki/Domain_name">domain names</a>, <a href="https://en.wikipedia.org/wiki/Autonomous_system_(Internet)">autonomous system numbers</a>, and <a href="https://en.wikipedia.org/wiki/IP_address">IP addresses</a>). Unlike WHOIS, RDAP provides:</p>
<ul>
<li>A machine-readable representation of registration data;</li>
<li>Differentiated access;</li>
<li>Structured request and response semantics;</li>
<li>Internationalisation;</li>
<li>Extensibility.</li>
</ul>
<p><strong>RDAP.org</strong> aims to support users and developers of RDAP clients by providing a "bootstrap server", i.e. single end point for RDAP queries. RDAP.org aggregates information about all known RDAP servers. RDAP clients can send RDAP queries to RDAP.org, which will then redirect requests to the appropriate RDAP service.</p>
<h2>How To Use RDAP.org</h2>
<h3>Client Implementers</h3>
<p>If you are developing an RDAP client, configure it to send HTTP requests to <tt>https://rdap.org/<type>/<object></tt>, where <tt><type></tt> is the object type (one of <tt>domain</tt>, <tt>ip</tt>, <tt>autnum</tt>, <tt>entity</tt> etc) and <tt><object></tt> is the object identifier (eg <a href="https://client.rdap.org/?type=domain&object=example.com"><tt>example.com</tt></a>, <a href="https://client.rdap.org/?type=ip&object=192.168.0.1"><tt>192.168.0.1</tt></a>, <a href="https://client.rdap.org/?type=autnum&object=64496"><tt>64496</tt></a>, etc).</p>
<h3>HTTP Status Codes</h3>
<ul>
<li><tt>302</tt> – occurs when RDAP.org knows of an RDAP service which is authoritative for the requested resource. Follow the URL listed in the <tt>Location</tt> header.</li>
<li><tt>400</tt> – occurs when RDAP.org receives an invalid request (malformed path, unsupported object type, invalid IP address, etc).</li>
<li><tt>403</tt> – occurs if you've been blocked due to abuse or other misbehaviour.</li>
<li><tt>404</tt> – occurs when RDAP.org doesn’t know of an RDAP service which is authoritative for the requested resource. RDAP.org only knows about RDAP servers that are <a href="https://www.iana.org/assignments/rdap-dns/rdap-dns.xhtml">registered with IANA</a>.</li>
<li><tt>500</tt> – occurs when RDAP.org is broken in some way.</li>
</ul>
<p>Note that these status codes only apply to the RDAP.org service itself, not the registry RDAP services themselves.</p>
<h3>IANA RDAP Service</h3>
<p><a href="https://www.iana.org">IANA</a> has recently launched an RDAP service. Each TLD has its own RDAP record at <a href="javascript:window.open('https://client.rdap.org/?type=tld&object='+escape(prompt('Enter TLD:')));void(0)"><tt>https://rdap.iana.org/domain/{TLD}</tt></a> <em>(<tt>root.rdap.org/domain</tt> now redirects to this server)</em>. You can also get an RDAP search result listing <em>all</em> TLDs using <a href="https://root.rdap.org/domains">https://root.rdap.org/domains</a>.
<a name="additional"></a>
<h3>Additional Resources</h3>
<p>Apart from the DNS, ASN and IP registries which are listed in the IANA registry, and IANA's own RDAP server, RDAP.ORG also provides an RDAP service for <strong>ICANN-accredited registrars</strong>. You can obtain RDAP records for ICANN-accredited registrars at <a href="javascript:window.open('https://client.rdap.org/?type=registrar&object='+escape(prompt('Enter registrar IANA ID:')));void(0)"><tt>https://registrars.rdap.org/entity/{NNNN}-iana</tt></a> where <tt>{NNNN}</tt> is the numeric <a href="https://www.iana.org/assignments/registrar-ids/">IANA ID</a>. These records are synthesised from data published by IANA and ICANN.</p>
<h3>References</h3>
<p>These are the authoritative references for the RDAP protocol specifications:</p>
<ul>
<li><a href="https://tools.ietf.org/html/rfc7480">RFC 7480: HTTP Usage in the Registration Data Access Protocol (RDAP)</a></li>
<li><a href="https://tools.ietf.org/html/rfc7481">RFC 7481: Security Services for the Registration Data Access Protocol (RDAP)</a></li>
<li><a href="https://tools.ietf.org/html/rfc9083">RFC 9083: JSON Responses for the Registration Data Access Protocol (RDAP)</a></li>
<li><a href="https://tools.ietf.org/html/rfc9224">RFC 9224: Finding the Authoritative Registration Data (RDAP) Service</a></li>
<li><a href="https://tools.ietf.org/html/rfc8056">RFC 8056: Registration Data Access Protocol (RDAP) Object Tagging</a></li>
<li><a href="https://tools.ietf.org/html/rfc8977">RFC 8977: Registration Data Access Protocol (RDAP) Query Parameters for Result Sorting and Paging</a></li>
<li><a href="https://tools.ietf.org/html/rfc8982">RFC 8982: Registration Data Access Protocol (RDAP) Partial Response</a></li>
<li><a href="https://tools.ietf.org/html/rfc9082">RFC 9082: Registration Data Access Protocol (RDAP) Query Format</a></li>
<li><a href="https://tools.ietf.org/html/rfc9536">RFC 9536: Registration Data Access Protocol (RDAP) Reverse Search</a></li>
<li><a href="https://tools.ietf.org/html/rfc9537">RFC 9537: Redacted Fields in the Registration Data Access Protocol (RDAP) Response</a></li>
<li>All generic TLDs (and some ccTLDs) are compliant with the <a href="https://www.icann.org/gtld-rdap-profile">gTLD RDAP Profile</a>.</li>
<li>The <a href="https://nro.net">Number Resource Organization</a> (NRO) developed the <a href="https://bitbucket.org/nroecg/nro-rdap-profile/src/master/nro-rdap-profile.txt">NRO RDAP profile</a> for RIR RDAP services.</li>
</ul>
<p>Many RDAP servers have also implemented their own custom extensions, some of which may be found in the <a href="https://www.iana.org/assignments/rdap-extensions/rdap-extensions.xhtml">RDAP Extensions registry</a> at IANA.</p>
<h3>The RDAP Book</h3>
<p>Andy Newton, one of the creators of RDAP, has published <a href="https://rdap.rcode3.com/" target="new"><em>A Guide to the Registration Data Access Protocol (RDAP)</em></a>, which is a definitive guide to implementing, using, and understanding all aspects of RDAP.</p>
<h2>Privacy Considerations</h2>
<p>If you use RDAP.org to perform RDAP queries, your queries will be logged, alongside your IP address. These logs are not disclosed to anyone and are deleted within a few days. RDAP.org will not set any cookies in your browser.</p>
<h2>Feedback</h2>
<p>If you would like to submit feedback, please email <a href="mailto:[email protected]" id="feedback-link">[email protected]</a>.</p>
<h2>Supporting RDAP.ORG</h2>
<p>If your organisation depends on RDAP.org, then please consider <a href="https://ko-fi.com/rdaporg" target="_blank">supporting it</a>, since it's not free to operate and requires ongoing maintenance and management.</p>
<h2>About RDAP.org</h2>
<p>You can review the code which RDAP.org uses on <a href="https://github.com/rdap-org/rdap.org">GitHub</a>.</p>
<p>RDAP.org is maintained by me, <a href="https://gavinbrown.xyz">Gavin Brown</a>. While I am currently an employee of ICANN, I run this service in my own time and at my own cost.</p>
<script>
document.getElementById('object').focus();
</script>